Ratepay: DPA, subprocessors and transfers

What to put in your subprocessor list

A ready row. Replace the purpose with what your client actually uses Ratepay for.

Questions people ask about Ratepay

Where is Ratepay's DPA?

Ratepay publishes its customer data processing agreement at https://docs.ratepay.com/docs/legal/b_ratepays_terms_for_merchants/data_processing_agreement/english_version. We last opened that link on 22 October 2026.

Is Ratepay's DPA the same thing as a data processing addendum?

Yes. A data processing agreement and a data processing addendum are two names for the document Article 28 of the GDPR requires between a controller and a processor; vendors use both, and some call it processor terms. What it has to contain does not change with the name. Ratepay's is at https://docs.ratepay.com/docs/legal/b_ratepays_terms_for_merchants/data_processing_agreement/english_version.

Which legal entity does Ratepay contract through?

Ratepay GmbH, registered in Germany. That is the name to put in a record of processing or a sub-processor list, not the brand.

Does sending personal data to Ratepay count as a transfer out of the EEA?

No. Ratepay GmbH is registered in Germany, inside the EEA, so no transfer mechanism is needed to reach it. Where it sends personal data on to is a separate question, and one for its own sub-processor list.

Where to go next

Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.

• Vendors contracting from Germany25 in the registry
• The vendor registryLegal entities, transfer mechanisms and DPA links, checked by a person
• Download the registry as a CSVFree, for a spreadsheet
• Guides for privacy practicesHow the work is actually done

Other payments

Six of them. All payments in the registry.

• Access Systems (UK)GB
• Adapty TechUS
• AdyenNL
• Buypass ASNO
• ChargebeeUS
• ChargehoundUS