Merchant API
Rotate a webhook signing secret

Rotate a webhook signing secret

Rotate the signing secret for a specific webhook.

For more information, see Tutorials: Verify the payload signature.


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.


Path Parameters
Path Parameters

The ID of the webhook.

Request body
Body object

Possible values: <= P7D

The expiration period of the signing secret in the ISO 8601 format.

If defined, when the signing secret is rotated, it continues to be valid until the expiration period passes. Otherwise, it is invalidated immediately.

Maximum expiration period is 7 days.



Response body
Body object

The ID of the webhook.

Your webhook's URL to which event notifications will be sent.

Must be a valid HTTP or HTTPS URL, capable of receiving POST requests.


List of event types that the webhook is configured to listen to.

The signing secret for the webhook. Use it to verify the signature for the webhook's request payload.

Was this page helpful?