Merchant API
Create a customer

Create a customer

Create a customer that has the information in the body of the request.


If you wish to save a customer's payment details using any of the available payment methods on the Revolut Checkout Widget (Revolut Pay, Card payments), you need to meet one of the following requirements:

  • Have a customer object with email and assign it to the order by providing
  • Create a new customer with, at least, during order creation

For more information, see: Charge a customer's saved payment method.


Each Merchant API request must contain an authorization header in the following format to make a call:

'Authorization: Bearer <yourSecretApiKey>'

Before you start, ensure that you've successfully applied for a Merchant Account in your Revolut Business Account.

The Public key is on the same path in your Revolut Business account as the Secret key. There are two different functions for each:

  • Public key should be provided with payment methods at checkout
  • Secret key is used as a part of the authorization header for all server calls, e.g., creating order

Complete the following steps to generate the Production API keys (Secret, Public):

  1. Log in to your Revolut Business portal.
  2. On the top left corner, click your account name, click APIs then select Merchant API.
  3. Under the Production API Secret key and Production API Public key sections you will find the API keys needed. If it's your first time on this page, you will need to click the Generate button to create your unique API keys.

You can also use this link to directly open the Merchant API page.

Merchant API - Settings


Use these keys only for the production environment. For the Revolut Business Sandbox environment, use the sandbox API keys.



This authentication protocol is used exclusively when using Fast checkout.

Connection over HTTPS is using SSL authentication. For successful authentication, your system's certificate should be issued by a Public Certificate Authority (PCA) and your system should trust Revolut's public certificate.



This authentication protocol is used exclusively when using Fast checkout.

Data integrity and authorship will be verified using a payload-based signature. The response of a successful URL registration for address validation (see: Register address validation for Fast checkout) will contain a secret signing key.

The signing key will be used by Revolut to compute a Hash-based Message Authentication Code (HMAC) payload signature whenever the registered URL is called, which should be verified by your backend.


Header Parameters
Header Parameters

This parameter accepts the Merchant API Secret key to authorise requests coming from the merchant's backend.

It ensures that ensures that each request is authenticated and authorised by verifying the secret key. The secret key should be included in all request headers as a Bearer token.


For more information, see: Authorization

Request body
Body object

The full name of the customer.

The name of the customer's business.

The email address of the customer.


Uniqueness of customer's email address is not enforced. This means, you can create multiple customer objects with the same email address.

The phone number of the customer in E.164 format.



Response body
Body object

Permanent customer ID used to retrieve, update, and delete a customer.

The full name of the customer.

The name of the customer's business.

The phone number of the customer.

The date and time the customer was created.

The data and time the customer was last updated.

The email address of the customer.

Was this page helpful?