Get your Partner ID, credentials, and template references in one exchange with the onboarding team.
This page walks you through onboarding - one email to the Revolut Wallet team gets you everything you need to start building.
How it works
Revolut gives you a set of components that together let you create, update, and auto-provision passes. Here's what each one does and where you'll use it:
| Component | What it is | Where you'll use it |
|---|---|---|
| Partner ID | Identifies your integration to Revolut | All API calls to the Partner API |
| API credentials | Authentication keys for the Partner API | Every call you make to Revolut-hosted endpoints |
template_id | Visual branding and layout for a pass design, set up by Revolut | Pass creation (POST /passes) |
| Callback base URL | Base URL where you host Wallet Partner Callbacks endpoints | Only for transaction results or poll-based pass updates |
| Merchant ID | Card acceptor identifier (DE 42 in ISO 8583 messaging) | Transaction results - Revolut uses it to match card transactions to you |
| Acquiring Institution ID | Bank or processor that acquired the transaction (DE 32 in ISO 8583 messaging) | Transaction results - Revolut uses it to match card transactions to you |
The onboarding process is a single exchange: you email the Revolut Wallet team with your business details and merchant identifiers, Revolut provisions your Partner ID, API credentials, sandbox URLs, and template_id, and then you configure authentication on both sides. If you're implementing the Wallet Partner Callbacks API, you also register your callback base URL.
Environments
Use the sandbox environment to build and validate your integration end to end before going live. Once your integration passes testing, switch to production.
| Environment | Base URL | Purpose |
|---|---|---|
| Sandbox | https://sandbox-partner.wallet.revolut.com | Build and validate end to end |
| Production | https://partner.wallet.revolut.com | After go-live |
Before you begin
- Have your business details ready (company name, use case, expected volume)
- Know your Merchant ID (card acceptor identifier, also known as DE 42 in ISO 8583 messaging)
- Know your Acquiring Institution ID (identifier of the bank or processor that acquired the transaction, also known as DE 32 in ISO 8583 messaging)
Onboard your business
1. Request onboarding
Email revwallet-partner-onboarding@revolut.com with your business details and the merchant identifiers Revolut uses to match card transactions: your Merchant ID and Acquiring Institution ID.
Revolut reviews your details and provisions your integration resources.
2. Receive your credentials
Revolut sends your Partner ID, API credentials, sandbox URLs, and a template_id for each pass design Revolut sets up for you.
With your credentials in hand, configure authentication so both sides can verify each other's API calls.
3. Set up authentication
Revolut registers your authentication method during onboarding. Authenticate as described under Authentication in the Partner API reference. For endpoints you host, Revolut authenticates to you — validate its credentials and reject anything else.
Authentication is configured on both sides. If you're implementing the Wallet Partner Callbacks API, there's one final step.
4. Register your callback base URL
Register your callback base URL with the Revolut Wallet team. You only need this if you implement the Wallet Partner Callbacks.
What's next
You're now ready to create your first pass.