Skip to content
Paul Walsh

API integration · Revolut Business

Revolut Business API integration

Pay customers and contractors from your Revolut Business account automatically, with the safeguards that make it safe to run. Each payment is checked against the account holder's name and needs a code sent by text before it goes. I built and ran this in production for a UK trade-in business. Quoted up front, and you own the code.

  • From £995, agreed before any work
  • Built and run in production for a trade-in business
  • Safeguards built in, not sold as extras

Get a quote

I'll reply within 24 hours with a price.

Your details are only used to reply to you.

Or WhatsApp / text 07398 946 380

Prices

Every project is different, so these are starting prices. You get a written quote before any work starts, then 50% to begin and 50% when you're happy with it.

Read-only

Transactions and balances in your system

From

£9953–5 days

  • Revolut OAuth sign-in
  • Transaction history with filtering
  • Balances in every currency
  • Webhooks for transaction events
  • Data sent to your platform or database
Get a quote for Read-only
Most popular

Payments automation

Payouts fired from your platform, safely

From

£2,995about 2 weeks

  • Everything in Read-only
  • Payees created with name checks
  • Bank details validated before sending
  • SMS one-time code before each payment
  • Payment limits and unusual-activity checks
  • Duplicate payment protection
  • Full audit log
Get a quote for Payments automation

Payments + Xero

Payouts reconciled in Xero automatically

From

£3,495about 2.5 weeks

  • Everything in Payments automation
  • Xero connection
  • Payments matched to invoices
  • Xero updated when payments confirm
  • Payouts recorded as bank transactions
Get a quote for Payments + Xero

Retainer

Optional, once the integration is live

From

£49per month

  • API health monitoring
  • Revolut API version updates
  • Twilio credential management
  • Immediate alerts on anything unusual
Get a quote for Retainer

What the Revolut Business API gives you

The Revolut Business API lets your platform send payments out of your Revolut Business account, manage saved payees, read transactions and hear about payment events straight away. This is about paying money out, not taking card payments (that's Stripe or GoCardless). See the Revolut Business API guide.

Who it's for

  • Phone, laptop and electronics buyback sites The device is graded and accepted, the bank details are checked, the code is confirmed, the payment goes and the customer is told, so same-day payment becomes realistic. See automating payments with the Revolut API.
  • Gold and jewellery buyers Higher-value payments with strict name matching, a code on every payment and a full audit trail.
  • Car buying and part-exchange platforms Bank details checked before inspection day, so the payment can go the moment a price is agreed, with extra approval for large amounts if you want it.
  • Contractor and freelancer payouts Amounts taken from your system and paid out on each payment run, with manual review only when a safeguard flags something.
  • Revolut and Xero together Every payment out recorded in Xero automatically, with no CSV exports.

The safeguards

A bug in most integrations is an inconvenience. A bug in a payment system can send real money to the wrong place, so every payout build includes:

  • A code by text before each payment It's sent to your approver through Twilio, expires after 10 minutes and locks after 5 wrong attempts. No code, no payment.
  • Name checks The account holder's name is compared with the customer's, allowing for initials and hyphenated names. Anything that doesn't match is held for review.
  • Bank detail validation The sort code and account number are checked before anything is sent to Revolut, catching typos straight away.
  • Duplicate protection The same order can never be paid twice, even if a request is retried.
  • Limits Caps on single payments and on daily and weekly totals, plus checks for unusual patterns such as lots of new payees in a short time.
  • A full audit log Every attempt, check result, code verification and Revolut response is recorded against the order.

How it's built

Everything is built and tested against Revolut's sandbox first, with every safeguard proven before a live account is connected. Then a few small real payments are made to check the whole flow before it goes into full use. You get documentation on how the flow works and how to change the limits.

Not included: your Revolut Business account and API access, your Twilio account and its per-text cost, your Xero subscription, and the business decisions themselves. The system makes payments safely. You still decide who gets paid, and KYC and AML checks stay your responsibility.

Payment is 50% to start and the balance on completion. For what drives the price, read what a Revolut integration costs.

How to get a price

Send a short written spec by WhatsApp, text, email or the form: what triggers a payment, roughly how many a day, the usual amounts and your platform. I'll reply within 24 hours with a quote.

Guides

Questions

Is the text message code really necessary?

Yes, and I won't build payouts without it. A system that can send bank transfers with no human check will one day send money somewhere it shouldn't, whether through a bug or a hacked account. The code adds seconds, and it's the most important protection there is.

What if the account name doesn't match?

The payment is held for your team to review. They see the customer's name next to the account holder's name and can approve it (initials instead of a full name, say), ask the customer for the right details, or look into it further.

Can it handle 200 or more payments a day?

Yes, that's what it was built for. Payments are queued and sent within Revolut's rate limits, so busy periods don't back anything up.

Which Revolut plan do I need?

API access comes with Revolut's business plans, and the payment limits through the API depend on your plan. The integration is set up within your plan's limits.

Can it pay international accounts?

Yes. International transfers need extra checks and the name check works differently, so they're quoted separately if you need them.

How long does a build take?

Read-only takes 3–5 days, payments automation about 2 weeks and payments with Xero about 2.5 weeks. The extra time goes on testing every safeguard before any real money moves.

Need this built into your system?

Quicker to message? WhatsApp or text 07398 946 380, or email paul@paul-walsh.co.uk.

Your details are only used to reply to you.