Revolut Merchant is Revolut's online payments platform that lets businesses accept card and alternative payments, manage orders and customers, handle refunds and disputes, and run subscriptions through the Revolut Merchant API. This connector uses secret API key authentication to move order, payment, and customer data between Revolut Merchant and Nexla.
Power end-to-end data operations for your Revolut Merchant API with Nexla. Our bi-directional Revolut Merchant connector is purpose-built for Revolut Merchant, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Revolut Merchant or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Revolut Merchant workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Revolut Merchant credential, you need a Revolut Business account with a Merchant account enabled, and a Merchant API Secret key. Revolut Merchant authenticates every request with this secret key, sent in the Authorization header as a Bearer token.
Open the Merchant area from the account menu, then go to APIs > Merchant API (also reachable from the Merchant overview).
Click Generate to create your Production Merchant API Secret key. Use Sandbox API keys when testing against the Revolut Sandbox environment.
Copy the Secret key immediately and store it securely. Revolut shows the full secret only once at creation time.
The Secret key is used for all server-side Merchant API calls and is sent in the Authorization: Bearer <yourSecretApiKey> header. Keep it confidential; if it is ever exposed, revoke it in your Revolut Business Merchant API settings and generate a new one. For more details, see the Revolut Merchant API Documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Revolut Merchant API Secret key in the API Key Value field. This is the Secret key you obtained in Prerequisites. Nexla sends this value in the Authorization header for all requests to the Revolut Merchant API.
Your Merchant API Secret key grants access to your Revolut Merchant account and should be treated as sensitive information. If it is compromised, revoke it in your Revolut Business Merchant API settings and generate a new one.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Revolut Merchant connector tile, then select the credential that will be used to connect to Revolut Merchant, and click Next; or, create a new Revolut Merchant credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Revolut Merchant endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] Retrieve an order list
This endpoint template retrieves data from the retrieve an order list endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Retrieve a list of orders from your Revolut Merchant account, including order IDs, amounts, currencies, states, and associated customer details.
This endpoint template retrieves data from the create an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Create a new order in your Revolut Merchant account and retrieve the resulting order object, including its ID and hosted checkout token.
This endpoint template retrieves data from the retrieve an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Retrieve the full details of a single order by its ID, including its current state, amount, and payment information.
This endpoint template retrieves data from the update an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Update the details of an existing order, such as its amount or metadata, before it is completed.
This endpoint template retrieves data from the increment authorisation endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Increase the authorised amount on an existing order that was created with a manual capture flow.
This endpoint template retrieves data from the capture an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Capture the funds for an order that was previously authorised, completing the payment.
This endpoint template retrieves data from the cancel an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Cancel an order that has been authorised but not yet captured, releasing the held funds.
This endpoint template retrieves data from the refund an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Issue a full or partial refund against a captured order and retrieve the resulting refund details.
This endpoint template retrieves data from the retrieve payment list of an order endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Retrieve the list of payments associated with a specific order, including payment states and amounts.
This endpoint template retrieves data from the retrieve a customer list endpoint of the Revolut Merchant API. Use this template to bring the returned records into Nexla for analysis, reporting, or integration with other systems.
Retrieve a list of customers stored in your Revolut Merchant account, including their IDs, contact details, and saved payment methods.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Revolut Merchant data sources can also be manually configured to ingest data from any valid Revolut Merchant API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Revolut Merchant data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Revolut Merchant destination, and select the Send to Destination option from the menu. Select the Revolut Merchant connector from the list of available destination connectors, then select the credential that will be used to connect to Revolut Merchant, and click Next; or, create a new Revolut Merchant credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Revolut Merchant endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Pay for an order
This endpoint template sends records from a Nexset to the pay for an order endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Submit a payment for an existing order using a saved customer payment method or supplied payment details.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Create a customer
This endpoint template sends records from a Nexset to the create a customer endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Create a new customer record in your Revolut Merchant account from Nexset records, storing details such as name, email, and phone.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Delete a customer
This endpoint template sends records from a Nexset to the delete a customer endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Delete an existing customer record from your Revolut Merchant account by its customer ID.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Update a customer's payment method
This endpoint template sends records from a Nexset to the update a customer's payment method endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Update the saved payment method details for an existing customer.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Delete a customer's payment method
This endpoint template sends records from a Nexset to the delete a customer's payment method endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Remove a saved payment method from an existing customer record.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Accept a dispute
This endpoint template sends records from a Nexset to the accept a dispute endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Accept a payment dispute, acknowledging the chargeback rather than contesting it.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Upload evidence for a dispute
This endpoint template sends records from a Nexset to the upload evidence for a dispute endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Upload supporting evidence for a payment dispute you intend to challenge.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Challenge a dispute
This endpoint template sends records from a Nexset to the challenge a dispute endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Submit a challenge against a payment dispute, contesting the chargeback with the uploaded evidence.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Create a subscription
This endpoint template sends records from a Nexset to the create a subscription endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Create a new recurring subscription for a customer, enabling scheduled billing against a saved payment method.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
[Rest API] Update a subscription
This endpoint template sends records from a Nexset to the update a subscription endpoint of the Revolut Merchant API. Use this template to push data from your Nexla flows into your Revolut Merchant account.
Update the details of an existing subscription, such as its amount, interval, or status.
Each record from your Nexset is sent as a separate API request. The request body must match the format expected by the Revolut Merchant API. For detailed information about request body formats and available fields, see the Revolut Merchant API Documentation.
Revolut Merchant destinations can also be manually configured to send data to any valid Revolut Merchant API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Revolut Merchant APIs expect JSON format for most operations. For update operations, include the ID of the object to be updated in the request URL.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Revolut Merchant endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Revolut Merchant endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
