BillingServ v3.1.8 is now available. This update brings two new integrations, a clearer place to review fraud information, and a simpler way for PHP developers to build on the BillingServ API.
The headline additions are Revolut and FraudRecord. We have also launched our official PHP SDK, added GDPR data exports and a searchable Country/County API, and made smaller improvements to checkout and API responses.
Two new integrations, with different jobs
Accept card payments through Revolut
You rarely want to rely on one payment route. Your customers have different preferences, and the right option can depend on where they are based and how they pay.
Revolut is now available as a BillingServ payment gateway. Your customers can pay the invoices you send through BillingServ using Revolut's embedded card checkout. They can save a card for future payments, and you can test the integration before switching to live mode.
For you and your team, the important part is that the payment remains connected to the right customer, order and invoice context. You get another card payment option without creating a separate billing process around it.
Use FraudRecord to add more context to fraud review
FraudRecord takes a different role. When you enable it, BillingServ can run a lookup on your customer and order during checkout and store the result with the relevant billing records.
BillingServ normalises and repeatedly hashes identity values such as your customer's email, name and username before sending the query. You can review the approval or review status, score, report count, confidence, history score and query ID when available.
The current FraudRecord integration runs in shadow mode. That means the result gives your team another signal to review, but it does not change the existing checkout decision. The new Fraud & Risk tab in your customer profiles brings FraudRecord reports and FraudLabs Pro results together in one place.
See how the FraudRecord integration works or explore the FraudLabs Pro integration.
Build on BillingServ with the official PHP SDK
If you use BillingServ as part of a wider application, you should not have to rebuild the same HTTP client and error handling every time you connect your customer portal, provisioning system or internal tool.
The new BillingServ PHP SDK is the official Composer package for the BillingServ v2 API. It handles authentication, JSON requests, response decoding and common API errors, while exposing resource clients for the parts of BillingServ your application needs.
composer require billingserv/php-sdkThe SDK supports PHP 8.3 and later and gives you resource clients for customer records, invoices, quotes, orders, packages, hosted checkout, domain availability, countries, counties, currencies, usage metering, reports, support tickets, VPN services, software licensing and more.
It also includes support for idempotency keys on relevant write operations, typed API exceptions, rate-limit handling and signed webhook verification. Keep the merchant API key on your server, then use your own application authentication for your customers.
Read the PHP SDK documentation to install the package and see examples, or go straight to the BillingServ API v2 reference when you need endpoint-level details.
A better foundation for custom billing workflows
The SDK is part of a broader improvement to the API. v3.1.8 makes success and error handling clearer across the API, which makes it easier to understand what happened after a request and decide what your application should do next.
We have also added a searchable Country/County API. That is useful when you are building your own signup flow, your customer portal or hosted checkout around BillingServ and need consistent address data instead of hard-coded lists.
If you are building a metered product, the API works alongside usage-based billing, including usage events, allowances and overage billing. If you run a broader custom billing operation, the cloud billing systems use case shows how those building blocks fit together.
More control over your customer data
GDPR data exports are now available to make it easier to provide your customers with a copy of their personal data when they request it. It is a practical addition, but an important one if you need a clear process for handling your customer data requests as your business grows.
Small improvements that remove everyday friction
Alongside the larger additions, v3.1.8 lets your customers delete saved cards directly from checkout, improves API success and error responses, and includes general tidy-up and stability work across the platform.
What to try first
If you take card payments, start with the new Revolut billing integration and review the wider BillingServ integrations directory.
If you are building your own customer experience, install the PHP SDK and use the API v2 documentation as your reference. You can use the same platform for your invoices and payments in the dashboard, or connect it to a custom application when that better suits your business.
BillingServ v3.1.8 gives you more ways to collect payments, more context around risk and more control over how billing connects to the rest of your product. If you are comparing billing platforms, see BillingServ pricing or start a 14-day trial with no card required.