Set up the Sandbox environment to test the integration before you push it to the production environment.
opensslcommand to generate a CSR.
You may also create the CSR using the command below, by providing your own application name:
openssl req -new -newkey rsa:2048 -nodes -out revolut.csr -keyout private.key -subj '/C=GB/ST=/L=/O=<YOUR APP NAME>/OU=001580000103UAvAAM/CN=2kiXQyo0tedjW2somjSgH7' -sha256 -outform der
The Overview tab of your application on the developer portal displays a
Client ID you can use in the Sandbox environment.
If you have an OBIE/eIDAS certificate, you can upload the certificate in the Developer Portal and register a production application without any further approval from Revolut. You are returned a
client_id that you can use to make requests to our API.
If you are looking to become a Revolut Partner, you must submit a request for your application to be approved via the Developer Portal. On successful approval of your application, you are returned production certificates to be used on our API.
transport.derin the directory where you stored your own certificate in Generate CSR.
You need to convert the signing and transport certificates to
openssl x509 -inform der -in transport.der -out transport.pem
openssl x509 -inform der -in signing.der -out signing.pem
Your certificate directory should now contain these 6 files:
"n": "<your n claim value>",
"kid": "<your KID value>",
openssl x509 -noout -modulus -in signing.pem | cut -c 9- | xxd -r -p | base64 | tr '/+' '_-' | tr -d '='
n claimvalue in the corresponding JSON key.
For testing purpose, you may host the JSON content on Pastebin and use a public address such as
You can use the following form to check if your JWK is valid. Copy and paste the full content of your JWK for a quick validation.
You are ready to start requesting user consents and make API calls to our endpoints. For more information, see our tutorials to walk you through the steps for different use cases.
You can also set up the production environment for your application.