- Ratepay Overview & Supported Regions: docs.adyen.com – Ratepay
- API-Only Integration: docs.adyen.com – API Only
- Web Components Integration: docs.adyen.com – Web Component
- Drop-in Integration: docs.adyen.com – Drop-in
Adyen is a global payment platform that provides processing, risk management, and acquiring services for online and in-store payments.
When integrating Ratepay via Adyen:
- Adyen acts as the payment service provider (PSP)
- All communication with Ratepay and risk evaluation is handled through Adyen
- you manage payments and transactions via the Adyen Customer Area
All implementation details and updates are maintained by Adyen in their official documentation.
You can enable Ratepay via Adyen using one of the following models:
| Integration Type | Description |
|---|---|
| API-Only | Build your own checkout form and call Adyen endpoints directly. |
| Drop-in UI | Prebuilt Adyen checkout interface including Ratepay. |
| Web Components | Use Adyen’s frontend components for secure data collection. |
Ratepay requires the following data:
- First & last name
- Date of birth
- Phone number
- Billing address
- Delivery address (if different from billing)
Missing data may result in declined payments. See also Adyen API guide
Device fingerprinting is mandatory:
- Generate and collect during checkout
- Include in the Adyen payment request
- Follow Ratepay guide: Device Fingerprinting Documentation
Incorrect implementation may lead to declined payments. See also Adyen API guide
{
"paymentMethod": { "type": "ratepay" },
"deviceFingerprint": "<generated_fingerprint>",
"shopperEmail": "shopper@example.com",
"billingAddress": { ... },
"deliveryAddress": { ... }
}- Retrieve payment methods
/paymentMethods → ratepay/ratepay_directdebit - Display Ratepay in checkout (based on chosen UI)
- Send payment request
/paymentsincluding buyer info & device fingerprint - Process response:
Authorised→ proceedRefused→ alternative payment optionCancelled→ buyer cancelled
- Capture after shipment
- Refunds / cancellations
For detailed API specs, see Adyen API guide.
When Ratepay declines a payment:
- Adyen event:
Refused - Contains
RefusalReasonRawwith Ratepay-specific codes
Note: Activate the optional response field to receive Ratepay-specific codes: BackOffice Settings → API Responses → activate
paymentResult_additionalData_refusalReasonRaw => 2100 : billing address not valid (150)2100→ Ratepay internal error codebilling address not valid→ description150→ Ratepay result code
References:
For supported countries and currencies please see: Availabilities through Adyen
Use the official Ratepay Go-Live Checklist.
Steps include:
- Ratepay enabled in Adyen (test & live)
- Buyer data correctly collected
- Device fingerprint implemented
- Payment methods correctly displayed
- Payment request & capture flows verified
- Result codes handled (Authorised, Refused, Cancelled)
- Refunds & cancellations tested
- Regional settings verified
Ensures all technical and compliance requirements are met before live operations.
- No direct Ratepay integration needed — use Adyen.
- Adyen manages risk checks, authorisation, and communication with Ratepay.
- Handle refusals via
RefusalReasonRaw.