Revolut Customers API
The Customers resource in the Merchant API is a pivotal tool for tracking and managing customer-related transactions within your e-commerce or retail platform. This resource provides a structured approach to customer management, enabling you to maintain a consistent record of customer transactions.A `Customer` object can be created using the [Create a customer](https://developer.revolut.com/docs/api/merchant#create-customer) endpoint and you can then retrieve, update and delete a customer using its `id`. `Customer` objects enable you to track multiple transactions in your system associated with the same customer in the Merchant API.You can save and store payment methods of a customer in the `payment_method` object, for more information, see: [Charge a customer's saved payment method](https://developer.revolut.com/docs/guides/merchant/optimise-checkout/save-payment-methods/charge-saved-payment-method). A merchant can store the details of the payment securely and group transactions from the same payment method in their system.A payment method is unique for each customer. For example, if the same card is used for a transaction by two different customers, two payment method objects are created linked to each customer.Similar principle applies when saving payment methods via Revolut Pay for merchant initiated transaction (MIT - useful for recurring payments). If a customer saves their details through Revolut Pay for MIT in separate sessions, each session will create a new payment method object linked to the customer.:::noteYou cannot create a payment method explicitly because they are generated as part of a payment. You can only retrieve, update or delete a payment method, or you can retrieve all payment methods of a customer.:::
Revolut Customers API is one of 46 APIs that Revolut publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Customers. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 9 operations across 4 paths, and defines 37 schemas. It is described by OpenAPI 3.2.0, at version 2026-04-20.
Requests are made against 2 base URLs: https://merchant.revolut.com, https://sandbox-merchant.revolut.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Revolut Customers API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as Authorization (Api-Key).
By default, every request must be authenticated.
Api-Key— Each Merchant API request must contain an authorization header in the following format: 'Authorization: Bearer ' To use this API, you need to generate API keys…
Paths & Operations 9
Across 4 paths, the API surfaces 9 operations — 2 DELETE, 4 GET, 2 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
The Customers resource in the Merchant API is a pivotal tool for tracking and managing customer-related transactions within your e-commerce or retail platform. This resource provi…
Schemas 37
The contract defines 37 schemas that model the data the API accepts and returns. The most detailed are Card-v2 (15 properties), Sepa-Direct-Debit-v2 (8 properties), Customer-v3 (7 properties), Customer-Created (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Revolut 12
Other APIs Revolut publishes across the network.
This is an independent, third-party profile of Revolut Customers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.