Revolut Business API · Payment Automation · UK
Revolut Business API Integration.
Automated customer payouts, counterparty management and transaction sync built on the Revolut Business API — with OTP verification, bank account name matching and payment safeguards that make automated money movement safe to run at scale. Built in production for a UK trade-in business. Fixed price.
Or describe what you need in one line — I’ll reply within one business day.
What it does
What the Revolut Business API provides.
The Revolut Business API provides programmatic access to your Revolut Business account — initiating outgoing payments, managing counterparties (saved bank accounts), retrieving transaction history and receiving real-time event notifications via webhooks. For businesses that need to pay customers or contractors from a Revolut Business account without manual dashboard intervention, this is the direct API to do it.
This is not the same as taking card payments — that’s Stripe or GoCardless. This is automating payments out of your Revolut Business account: paying customers for trade-ins, sending contractor payouts, automating refunds, syncing transactions to accounting. The integration runs on your server, connects to your Revolut Business account, and fires payments when your platform says to — with every safeguard required to make that safe.
Who it’s for
Who uses a Revolut Business API integration.
Mobile phone, laptop and electronics buyback sites
Customers send devices, you grade them, you pay. At 50–200 payments per day, manual Revolut transfers are unmanageable. The integration triggers payment automatically when a device is graded and accepted — bank details validated, name checked against the account holder, OTP verified, payment fired, customer notified. Same-day payment becomes operationally realistic rather than aspirational.
Gold, jewellery and precious metal buyers
Customers post items, you assess and make an offer, you pay. Individual payment values are higher, so the safeguards matter more. OTP on every payment regardless of amount, strict name matching, full audit trail. The integration can be configured conservatively for high-value use cases without compromising speed.
Car part-exchange and vehicle buying platforms
Online car buyers that need to settle large payments quickly after vehicle inspection. Settlement amounts vary and can be significant — the payment limit and dual-approval configuration for high-value payments is built to your requirements. Bank details verified before inspection day so payment can fire immediately on agreement.
Freelancer and contractor payout platforms
Agencies, staffing platforms and gig economy businesses paying contractors weekly or monthly. Payroll or earnings data from your system drives the payment amounts. Revolut API fires the transfers to each contractor’s bank account automatically on the payment run. Manual intervention only if a payment is flagged by a safeguard.
Businesses wanting Revolut transaction data in Xero
Transaction history pulled from Revolut Business automatically and reconciled in Xero — every payment out creates the corresponding Xero entry, incoming transactions sync to the bank feed. No CSV exports, no manual matching, accounts current in real time. Available as a standalone read-only integration or as part of the Payments + Xero tier.
Payment safeguards
Built to handle real money safely.
Unlike most API integrations where a bug causes an inconvenience, a bug in a payment system can send real money to the wrong place. These safeguards are non-negotiable in any payout integration — they are built in by default, not offered as optional extras.
OTP verification via SMS
Every payment requires a one-time password sent to the authorised approver’s mobile via Twilio SMS before it releases. Code expires in 10 minutes. 5 failed attempts locks the payment for manual review. No OTP, no payment — regardless of what else the system says. Twilio SMS ongoing cost (~5p per payment) is the client’s direct cost.
Bank account name matching
Revolut’s counterparty API returns the registered account holder name for the sort code and account number. This is compared against the customer’s name on the order. Exact or close match (handling initials, hyphenated names, common variations) proceeds. Mismatch flags for manual review with the discrepancy shown to your team.
Modulus checking
Sort code and account number combination validated mathematically before any API call. Invalid combinations caught and rejected immediately. This is the first line of defence against typos — it costs nothing and prevents a significant proportion of invalid payment attempts before they reach Revolut.
Duplicate detection
Idempotency keys on every payment creation request. Before creating a payment, the integration checks for an existing payment with the same order reference. Duplicate attempts return the existing payment status rather than creating a new payment. Protects against double-submission and webhook retry events.
Payment limits and velocity checks
Configurable individual payment cap, daily total cap and weekly total cap. Payments that would breach a limit are queued for manual approval. Velocity checks flag unusual patterns — too many new counterparties in a short window, or payments to new accounts at an unusual rate — for review before proceeding.
Full audit log
Every payment attempt logged with timestamp, destination account, amount, safeguard check results, OTP verification status, Revolut API response and order reference. The complete evidence trail for any payment query, dispute or financial review.
The process
How a Revolut Business API integration is built.
More rigorous than most API builds — every safeguard is designed and tested before connecting to a live Revolut account.
Scoping
We map the payment flow, define payment limits and approval thresholds, confirm the safeguard configuration appropriate for your payment values and volumes, and establish the OTP authoriser setup.
Fixed-price quote
Clear, itemised quote before work begins. Scope agreed in writing.
Revolut sandbox setup
OAuth authentication with RSA key pair, sandbox counterparty creation, payment flow built and all safeguards implemented and tested against the sandbox before touching live funds.
Twilio OTP integration
SMS OTP flow built alongside the Revolut integration — payment pending, OTP fired, code validation, payment release or lock. Tested end-to-end in sandbox.
Production testing and handover
Small number of real low-value test payments before full deployment. Full audit log verified. Documentation covering the payment flow, safeguard configuration and how to adjust limits. You own the code.
The deliverable
What’s included.
What I build
- Revolut OAuth 2.0 authentication with RSA key management
- Counterparty creation with name verification
- Bank account modulus validation
- Payment creation with pending state
- OTP verification via Twilio SMS before payment release
- Payment limit and velocity check logic
- Duplicate detection with idempotency keys
- Webhook handler for payment confirmation and failure
- Full audit log of all payment actions
- Transaction history retrieval and sync
- Xero reconciliation (if in scope)
- Technical handover document
What’s not included
- Revolut Business account — you need an active account with API access enabled
- Twilio account — free to set up; ~5p per OTP SMS paid directly to Twilio
- Xero subscription — required if Xero reconciliation is in scope
- Payment decisions — the system automates payment execution; business decisions (approve/reject a trade-in) remain with you
- KYC or AML compliance — your responsibility; the integration includes the technical safeguards only
Pricing
Fixed-price builds. Banking-grade rigour.
Revolut payment automation is priced higher than other integrations on this site because the stakes are higher. Safeguards are non-negotiable and built in at every tier that handles outgoing payments.
Read-Only
£995
~3–5 days
Transaction history retrieval, balance monitoring and data sync. Pull Revolut Business transaction data into your platform, dashboard or accounting system automatically. No outgoing payments — read only.
- OAuth 2.0 authentication
- Transaction history retrieval with filtering
- Multi-currency balance monitoring
- Webhook handler for transaction events
- Data push to your platform or database
- Outgoing payments
- Counterparty management
- Xero reconciliation
Payments Automation
£2,995
~2 weeks
The full automated payout system. Outgoing payments triggered from your platform with every safeguard built in — OTP via Twilio, bank account name matching, modulus checking, payment limits, duplicate detection and full audit logging. Built to run safely at scale.
- Everything in Read-Only
- Counterparty creation with name verification
- Modulus validation on bank details
- OTP verification via Twilio SMS
- Payment limits and velocity checks
- Duplicate detection (idempotency keys)
- Full audit log
- Webhook — confirmation and failure handling
Payments + Xero
£3,495
~2.5 weeks
Everything in Payments Automation plus automatic Xero reconciliation. When a Revolut payment confirms, the corresponding Xero invoice is marked paid or a bank transaction is created automatically. Keeps accounts current without manual matching.
- Everything in Payments Automation
- Xero OAuth connection
- Payment-to-invoice matching
- Xero payment creation on confirmation
- Revolut payout bank transaction in Xero
- Technical handover document
Payment terms: 50% on agreement, balance on completion. Twilio OTP SMS (~5p per payment) is an ongoing client cost paid directly to Twilio. Revolut Business API access requires your own active account with API access enabled in Business settings.
Common questions
Revolut Business API FAQ.
Is the OTP verification actually necessary?
Yes — and it won’t be built without it for the payments automation tier. A system that can fire bank transfers without any human verification step is a system waiting to send money somewhere it shouldn’t. The OTP is lightweight to use, adds seconds to the payment process, and is the most important protection against both code errors and account compromise. At low payment thresholds it can be configured to auto-approve, but the mechanism must exist.
What happens if the bank account name doesn’t match?
The payment is held and flagged for manual review. Your team sees the customer’s name, the account holder name from Revolut’s lookup, and the discrepancy. You can approve manually if satisfied it’s the same person (e.g. initials vs full name), reject and ask the customer for matching details, or escalate if the mismatch looks suspicious.
Can it handle high volumes — 200+ payments per day?
Yes — this is exactly the use case it was built for. Rate limit management ensures the integration doesn’t exceed Revolut’s API limits. The queue and processing architecture handles spikes without backing up. Payment limits are configurable daily totals, not per-call limits.
What Revolut Business plan is needed?
API access is available on Revolut’s Business plans. The specific payment limits available through the API vary by plan tier. Higher plan tiers have higher API payment limits. This is confirmed during scoping — the integration is configured within the limits of your plan.
Can it pay international bank accounts?
Yes — Revolut Business supports international transfers and the API can initiate them. IBAN-based international payments require additional validation and the name matching step works differently for international accounts. International payment scope is confirmed and priced during scoping.
How long does the build take?
Read-Only takes 3–5 days. Payments Automation takes approximately 2 weeks — the additional time reflects the safeguard implementation and thorough testing before connecting to live funds. Payments + Xero takes approximately 2.5 weeks.
Payment automation like this is best delivered as part of a bespoke website build, and supported by improving your search visibility so the right customers reach you.
Need Revolut payment automation built?
Describe your payment flow — what triggers a payment, how many per day, the typical amount range, and your platform. I’ll come back with a clear scoping response and a fixed price. No obligation.
