Revolut for Business

A company that banks with Revolut for Business cannot route native Webflow Ecommerce checkout through its Revolut Merchant account, because Webflow Ecommerce connects only to Stripe and PayPal. So a Revolut payment on a Webflow site always happens on a Revolut-hosted page or in a Revolut widget, and a server you run confirms it. Custom code runs in the visitor's browser, so a Revolut Secret API key can never live on a Webflow page.

Webflow's Code Embed element can host the Revolut browser SDK, and Webflow CMS collections can store records written by automation or a backend. Merchant API webhooks let that backend confirm fulfillment from completed orders.

How to integrate Revolut for Business with Webflow

What is Revolut for Business? Revolut for Business is a business account that can exchange 25+ currencies, per Revolut's own product page. A Merchant account, a sub-account of the Business account, accepts online payments by card, Revolut Pay, Apple Pay, Google Pay, and Pay by Bank. The separate Business API automates account operations such as listing transactions and initiating transfers.

The usual trigger is a sales or product page that must settle into an existing Revolut Business account. Revolut's no-code plugins target hosted ecommerce platforms such as Shopify and WooCommerce, and we found no Revolut plugin for Webflow. Each method below either redirects to a Revolut-hosted page or calls a server you control.

The Revolut for Business and Webflow integration supports four approaches:

• Payment Links: A Revolut-hosted checkout sits behind an ordinary Webflow button.
• Merchant Web SDK: The Revolut Pay button and the Checkout widget render inside a Code Embed element.
• Zapier and Make: These connect Revolut Business account activity to Webflow CMS actions without writing code.
• Webflow Data API and Revolut APIs: Your own server controls order creation, webhook handling, and CMS records, which requires server-side development.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Add Revolut Payment Links and checkout widgets to Webflow pages

Apply for a Merchant account at business.revolut.com/merchant. Submitting the application starts a Know Your Merchant review, and Revolut emails you when the account is approved. Payment Links need no code on Webflow, because the button is an ordinary link. The Revolut Pay button and the Checkout widget keep the customer on your page instead, and both receive an order token from a server endpoint.

Link a Webflow button to a Revolut Payment Link

No API key is involved in a dashboard-created Payment Link. It opens a Revolut-hosted checkout with the payment methods enabled for your Merchant account, and Webflow stores nothing about the payment. Revolut's own guide covers the flow in full, and the lesson button on this page opens it.

To add a Payment Link to a Webflow page:

1. Log in to Revolut Business, go to Merchant > Payment link, and click Create link.
2. Enter a Title, then set a fixed amount or let the customer set the amount.
3. Add an optional payment limit, expiry date, or custom field, and create the link.
4. Copy the link URL from the sharing options.
5. In Webflow, add a Button element, open its link settings, paste the URL, and publish the site.

The hosted checkout page supports:

• Payment methods: Customers see the methods enabled for your Merchant account.
• Branding: You can set a logo, a cover image, a button colour, and the business details shown at checkout.
• Multiple payments: A toggle lets one link accept more than one payment, with an optional payment limit or expiry date.
• QR code: The sharing options include a QR code for in-person scanning or printed material.

Dashboard links redirect to Revolut's default confirmation page after payment. A custom redirect_url exists only on orders created through the Merchant API, covered below. A Payment Link purchase also creates no Webflow Ecommerce order record or inventory change.

Mount the Revolut Pay button with a Code Embed element

The Merchant Web SDK (@revolut/checkout on npm) includes a revolutPay module that mounts a standalone Revolut Pay button. Revolut documents it in the Revolut Pay SDK guide. The button's createOrder callback must call a server you control, such as a Webflow Cloud app or a function on any serverless platform.

To mount the button:

1. Deploy a server endpoint that calls POST https://merchant.revolut.com/api/orders and returns the order token (see the API section below).
2. In Webflow, open Add panel > Advanced > Embed and drag the element onto the page.
3. Add a container such as <div id="revolut-pay-container"></div>, load the SDK, and paste the initialization:

const { revolutPay } = await RevolutCheckout.payments({
  publicToken: '<YOUR_PUBLIC_API_KEY>',
  locale: 'en',
})
revolutPay.mount('#revolut-pay-container', {
  currency: 'GBP',
  totalAmount: 1000,
  createOrder: async () => {
    const response = await fetch('/api/create-revolut-order') // your server endpoint
    const order = await response.json()
    return { publicId: order.token }
  },
})

4. Replace /api/create-revolut-order with the full HTTPS URL of your endpoint, then publish the site.

A Code Embed holds up to 50,000 characters. The button renders on the published site, outside the Webflow canvas, and totalAmount is in the currency's smallest unit, such as pence or cents.

Embed the Revolut Checkout widget

RevolutCheckout.embeddedCheckout() gathers the payment methods you enable into one widget that Revolut manages. Set their order and availability in the dashboard under your profile > Settings > Merchant > Revolut Checkout, not in code. Revolut's Checkout web guide covers the full flow.

To embed the widget:

1. Bundle @revolut/checkout, host the built file externally, and load it with a <script src> tag under Site settings > Custom code > Head code.
2. Place an empty <div> target and this initialization in a Code Embed on the checkout page:

const { destroy } = await RevolutCheckout.embeddedCheckout({
  publicToken: '<yourPublicApiKey>',
  mode: 'prod',
  locale: 'en',
})

3. Add the target selector and a createOrder function that calls your backend and returns { publicId: order.token }.
4. Wire onSuccess(), onError(), and onCancel() to page state only, then publish.

Revolut's guide states that you "must rely on webhooks for all critical backend logic, such as confirming the order, releasing digital goods, or starting the shipping process." If you enable Apple Pay, the same guide requires you to register your domain for Apple Pay before the button renders in the widget. Google Pay has no equivalent step in that guide.

Connect with Zapier or Make

Both tools work with Revolut Business account data, not Merchant account data, so checkout orders and Payment Links never reach them as triggers. The Revolut Business Zapier app has one trigger, New Transaction, which fires when you exchange, send, or receive money, plus a Find Account search. Zapier has no dedicated Revolut and Webflow pairing page, so you build the Zap yourself. Make lists Revolut Business modules beside its Webflow modules on one integration page, including a Create a Draft Payment action.

The available pairings are:

• Transaction log: The Zapier New Transaction trigger feeds a Webflow Create CMS Item action, so each transaction sent or received becomes a CMS record.
• Account details: The Zapier Find Account search adds account details to a Webflow CMS item in the same Zap.
• Queued payouts: Any Webflow trigger in Make can run Revolut Business Create a Draft Payment, which queues an outbound payment for a person to approve.
• Plan gate: Draft payments belong to the Business API, which Revolut offers on its Grow plan and above, so check your plan before building a Make scenario around them.

Neither tool can confirm a checkout payment, so use the API route below when fulfillment depends on one.

Build with the Webflow and Revolut APIs

A server-side implementation is required for custom redirects, reliable payment confirmation, and Webflow CMS order records. A Webflow Cloud app can host the route handlers, and any external serverless platform works as well.

The available APIs are:

• Revolut Merchant API: It handles orders, customers, payments, refunds, and webhooks for your Merchant account.
• Revolut Business API: It handles accounts, counterparties, transfers, and transactions on the Business account.
• Webflow Data API: It creates CMS items and reads form submissions.
• Webflow webhooks: They push site events, such as a new form submission, to your server in real time.

Merchant API requests authenticate with Authorization: Bearer <yourSecretApiKey> plus a Revolut-Api-Version header on the operations that require it. The Business API uses OAuth 2.0 with a JWT client assertion. Webflow Data API v2 accepts a Bearer site token or OAuth token at https://api.webflow.com/v2.

Create hosted checkout orders server-side

The response to an orders call contains a token for the widget and a checkout_url for redirects. Revolut's Hosted Checkout API guide describes the pattern, and the checkout_url is the payment link.

To create an order:

1. In Revolut Business, open the Merchant overview, select Merchant API, click Generate to create a Production API Secret key, and store it in an environment variable.
2. Call POST https://merchant.revolut.com/api/orders with Authorization: Bearer <yourSecretApiKey> and Revolut-Api-Version: {version}, using the version shown in Revolut's Merchant API reference. The body carries amount in the smallest currency unit and currency.
3. Add redirect_url to the body when you want the customer returned to a Webflow thank-you page.
4. Read id, token, state, and checkout_url from the response. Redirect the browser to checkout_url, or return token to the widget as publicId.
5. Treat the order as paid only when your webhook handler receives confirmation, as described in the next section.

Test against https://sandbox-merchant.revolut.com/ with sandbox keys before switching to production. Omitting the version header where it is required returns an error response. The Create an order endpoint now returns token as the public identifier, and Revolut marks the older endpoint that returned public_id as deprecated.

Record completed orders in the Webflow CMS via webhook

An ORDER_COMPLETED webhook is the reliable signal that money moved. Your server verifies it, fetches the order, and creates a live CMS item. A Collection List then renders those items as an order log, receipt page, or attendee roster. Revolut does not guarantee the delivery order of events, so key idempotency on order_id.

To sync orders into the CMS:

1. Register your HTTPS endpoint through the Merchant API webhooks endpoint, subscribing to ORDER_COMPLETED, and store the signing secret it returns. Revolut's webhooks guide caps a merchant at 10 webhook URLs.
2. On each delivery, verify the Revolut-Signature header with that signing secret, following Revolut's signature verification steps, before trusting the payload.
3. Parse the payload, which carries event, order_id, and merchant_order_ext_ref:

{
  "event": "ORDER_COMPLETED",
  "order_id": "9fc01989-3f61-4484-a5d9-ffe768531be9",
  "merchant_order_ext_ref": "Test #3928"
}

4. Fetch full details with GET https://merchant.revolut.com/api/orders/{order_id}. The event payload carries only the fields above, so this call is the source of truth.
5. Create the item with POST https://api.webflow.com/v2/collections/{collection_id}/items/live using a token with CMS:write scope. fieldData carries name and slug plus your custom fields, and /live publishes immediately.

Use POST /v2/collections/{collection_id}/items instead when you want a staged item for review before publishing. Check Revolut's Merchant API reference for the other order and dispute events before subscribing to them.

Reconcile Webflow form submissions with Business API transactions

Businesses that take bank transfers against a Webflow form, such as a quote request or booking form, can match submissions to incoming money automatically. The Webflow side pushes in real time through a form_submission webhook or pulls in batches. The Revolut side reads the Business account's transaction history.

To reconcile submissions:

1. Register POST https://api.webflow.com/v2/sites/{site_id}/webhooks with { "triggerType": "form_submission", "url": "..." }, adding a filter to target one form. The payload includes name, siteId, data, submittedAt, and formId.
2. Verify x-webflow-signature by computing a SHA-256 HMAC over timestamp + ":" + JSON.stringify(request_body) using x-webflow-timestamp. Reject requests older than 5 minutes.
3. Read money movements from the Business API transactions endpoint with an OAuth 2.0 Bearer token, or subscribe to Business API transaction webhooks.
4. Match the submission's reference field against the transaction reference, amount, and currency.
5. Write the result back with PATCH /v2/sites/{site_id}/form_submissions/{form_submission_id}, which updates hidden fields only and needs forms:write scope.

Business API access tokens expire after 40 minutes, and the refresh token issued at setup gets you a new one. If you enable the READ_SENSITIVE_CARD_DATA scope, set up IP whitelisting first, as Revolut requires. Batch pulls of GET /v2/sites/{site_id}/form_submissions return up to 100 submissions per page.

What you can build with the Revolut for Business Webflow integration

The implementation can stop at a hosted payment page or continue into webhook-driven fulfilment.

• Agency proposal pages with deposit buttons: A Webflow proposal page ends with a "Pay deposit" button linked to a Payment Link. The client pays a fixed amount or sets one on Revolut's hosted page, and the multiple-payments toggle lets one link serve every client.
• Event ticket pages: A Payment Link with a payment limit equal to venue capacity and an expiry date sells tickets from a Webflow event page. The QR code goes on printed posters, and an ORDER_COMPLETED webhook creates one CMS item per completed sale for a roster rendered in a Collection List.
• Revolut Pay product checkout: A Webflow product page mounts the Revolut Pay button in a Code Embed backed by a Webflow Cloud function, so Revolut users pay without leaving the page.
• Webhook-fulfilled digital products: A course or template shop creates the order server-side, receives ORDER_COMPLETED, and writes a live CMS item that opens access to a download page.

The same server pattern powers other Webflow Cloud apps, so build an invoice generator next if your clients also need billing documents.