Resources for Developers
Use our practical resources for developers to get started right away.
Instructions for custom integration
Learn how you can receive one-time or recurring payments directly in your system, on your website, or via your app.
Payrexx is compatible with all popular shop systems and CMS.
Guide for Developers of Platforms and Marketplaces
Find all necessary documentation and assistance to receive online payments through your platform or marketplace.
Frequently Asked Questions by Developers
Can I try Payrexx for free?
Yes, the first 30 days of the trial subscription are free. Simply sign up here and get started. No credit card is required.
How do I test an initial payment?
Activate the test mode in the payment provider settings. Afterwards, you can open a payment page via API or one of the integrated tools and conduct a test payment without any money flow. More about it here
Which programming languages are supported?
You can use our API with any language. You can find more information in the Payrexx API documentation.
For PHP, we also offer a ready-to-use SDK in our GitHub account.
Where can I find code examples?
In our PHP SDK, you will find ready-made PHP example codes for various use cases.
In the API documentation, you will find examples for every API call.
How are SCA (Strong Customer Authentication) and 3D Secure 2.0 handled in the checkout flow?
Payrexx automatically handles the complex requirements of the Payment Services Directive PSD2 (including SCA) for the developer.
For standard credit cards, the 3D Secure challenge flow is directly hosted and processed by the Payrexx gateway.
For wallets such as Google Pay or Click to Pay (Visa), Payrexx automatically uses modern, tokenised authentication methods (e.g. CRYPTOGRAM_3DS). Since this is already recognised by card issuers as strong authentication, the additional 3D Secure step in the checkout is completely eliminated (Frictionless Flow).
Does the API support the automatic processing of partial refunds?
Yes. Both full refunds (Refund) and partial refunds (Partial refund) are supported via API and in the Dashboard. The API's transaction object also returns the Boolean values refundable and partiallyRefundable, so the developer's system knows immediately if a partial booking is possible. In the case of a partial refund, the status of the transaction changes to partially-refunded. Webhooks are also triggered by these status changes.
How is idempotency ensured in API calls to avoid duplicate bookings?
To avoid duplicate bookings, developers must use the unique Payrexx uuid (transaction ID from Payrexx) or their own referenceId (order ID of the shop) provided during the transaction creation. Payrexx also recommends always using these IDs to verify webhooks against your own database.
What PCI-DSS compliance requirements apply when using the API or SDKs?
Payrexx is PCI-DSS Level 1 certified as a payment platform. When developers use the Payrexx Payment Gateway, the hosted payment pages (Pages) or plugins, their own servers do not encounter sensitive cardholder data (CHD - Cardholder Data). The entire sensitive payment flow is handled through Payrexx's servers, which significantly reduces the scope of PCI compliance for the comerciante (usually to a simple SAQ-A questionnaire).
