Accept Payments with the Revolut Gateway
If your business already banks with Revolut, sending card sales through a separate processor means another account, another payout to track and another dashboard to reconcile.
Stackless for FluentCart adds Revolut Merchant to FluentCart → Settings → Payments as Revolut (Stackless), with your own key. Buyers pay on Revolut’s hosted page, saved cards renew subscriptions, refunds work both ways and a signed webhook is set up for you. Revolut is a payment processor here, so you stay the seller and tax stays yours.
Run a test payment before you take live ones. This gateway was tested against a simulated Revolut API and hasn’t taken a sandbox or real payment.
Before You Start
- FluentCart 1.6.4 or newer.
- A Revolut Business account with a Merchant account, and a Merchant API secret key created without request signing. Stackless doesn’t support signed requests.
- A separate Revolut sandbox account and key for test orders.
- A public HTTPS site, so Revolut can deliver webhooks, and working WordPress scheduled tasks for renewals and payment checks.
- For automatic renewals, Revolut’s confirmation that merchant-initiated payments are allowed on your account.
Turn On the Gateway
- Go to FluentCart → Stackless and switch on Payment Gateways on the Stackless Dashboard. The switch saves at once.
- Open Settings on the Payment Gateways card, make sure Revolut is ticked under Gateways to add to FluentCart and click Save changes. Clearing it later takes it off checkout and keeps its settings saved.
- Open FluentCart → Settings → Payments and choose Manage on Revolut (Stackless).
Buyers see it as Revolut. The admin shows the Stackless label.
Connect Your Revolut Account
FluentCart’s store mode picks the key: Test order mode uses the sandbox and Live order mode uses production.
- On the Live credentials or Test credentials tab, click Open Revolut Business or Open Revolut sandbox. In that account, open the Merchant API settings and copy the secret key, which starts with
sk_. - Paste it into Live secret key or Sandbox secret key.
- Turn on Payment Activation and save.
Saving checks the key and says “Revolut connected.” when it works. The key needs read and write access to orders, payments, customers and webhooks, and read access to disputes.
Keys and signing secrets are stored encrypted. To keep them out of the database, define them in wp-config.php. A defined value hides its field:
define('GTFC_REVOLUT_LIVE_SECRET_KEY', 'sk_...');
define('GTFC_REVOLUT_LIVE_WEBHOOK_SECRET', 'wsk_...');
define('GTFC_REVOLUT_TEST_SECRET_KEY', 'sk_...');
define('GTFC_REVOLUT_TEST_WEBHOOK_SECRET', 'wsk_...');
Connect the Webhook
On a public HTTPS site, saving creates the webhook in each Revolut account you entered a key for and saves its signing secret. A webhook already at your URL is reused and gets any missing events.
https://yoursite.com/?fluent-cart=fct_payment_listener_ipn&method=gtfc_revolut
To add it with Revolut’s API instead, use that URL with these events, then paste the secret into Live webhook signing secret or Sandbox webhook signing secret:
ORDER_COMPLETEDORDER_AUTHORISEDORDER_CANCELLEDORDER_FAILEDORDER_PAYMENT_AUTHENTICATION_CHALLENGEDORDER_PAYMENT_DECLINEDORDER_PAYMENT_FAILEDDISPUTE_ACTION_REQUIREDDISPUTE_UNDER_REVIEWDISPUTE_WONDISPUTE_LOST
How the webhook behaves:
- The webhook confirms payments when the buyer closes the tab, settles renewal charges and brings refunds and disputes into FluentCart.
- Unsigned, badly signed or stale deliveries are refused. For the rest, Stackless reads the payment or dispute from Revolut before it changes an order.
- Revolut sends dispute events for live accounts only.
- In Live order mode, the gateway won’t save as active without a signing secret. A private test site can do without one, but refunds made in Revolut don’t arrive there.
- A copy of the live store never creates or changes the live webhook.
Run a Test Payment
Test order mode covers the whole store: buyers can’t pay with real cards and renewals of live subscriptions wait, so pick a quiet time or use a separate test site. Refunds and renewal charges only run on a site Stackless treats as the live store. Staging Copies explains how that’s decided.
- Put FluentCart in Test order mode, with the sandbox key saved.
- Place a one-time order with one of Revolut’s test cards and check that it turns paid.
- Refund it from FluentCart. Pay another order, refund that one in Revolut and check that the refund appears on the order.
- If you sell subscriptions, start one on a daily plan and check that the next day’s renewal charges the saved card.
- Switch to Live order mode, then make one small real payment and refund it.
What Buyers See
- Checkout says “You’ll finish paying securely with Revolut after you place the order.”
- A payment that saves no card opens Revolut’s hosted page, with the methods Revolut offers there.
- A payment that saves a card opens a page on your store first. The buyer clicks Agree and pay, or Agree and save card when nothing is due, and enters the card in Revolut’s window.
- Back on your site, Stackless reads the payment from Revolut before it marks the order paid. If Revolut is still processing, the receipt shows the real state.
- Placing the same order again reuses the open Revolut payment. If an earlier one might still go through, the buyer is asked to wait.
Subscriptions and Renewals
FluentCart schedules every renewal and works out its amount. No subscription is created at Revolut. What buyers get depends on Renewal Billing, in the Subscriptions section of FluentCart’s store settings. A change there affects new subscriptions only:
| Renewal Billing | Subscriptions paid with Revolut |
|---|---|
| Store Billing with Auto-charge saved payment methods | The first payment saves the card and FluentCart charges it on each renewal. A free trial saves the card for $0. |
| Store Billing without auto-charge | No card is saved, and the customer pays each renewal by link. Not offered when nothing is due today. |
| Gateway Billing with Allow all payment methods (Manual Fallback) | No card is saved, and the customer pays each renewal by link. Not offered when nothing is due today. |
| Gateway Billing without it | Revolut isn’t offered for new subscriptions. |
- Only cards renew. If a paid first order saves no card, the subscription moves to renewals paid by link. A free trial doesn’t start until a card is saved.
- A renewal the bank wants confirmed is emailed to the customer to pay.
- A declined renewal records Revolut’s reason on the order. One without a clear answer stays processing and is read back from Revolut before anything is charged again.
- Cancel in FluentCart. There’s no schedule to cancel at Revolut.
- Saved cards belong to the connected Revolut account. If you connect another account, they can’t be charged.
Refunds and Disputes
- Full and partial refunds from FluentCart go to Revolut.
- A completed refund made in Revolut Business is recorded on the order once, by webhook.
- If Revolut doesn’t confirm a refund, refund the same amount again. It can’t go out twice.
- A refund that fails after it was recorded adds an order note saying the customer didn’t receive it.
- A dispute is marked on the payment and noted on the order. Answer it in Revolut Business. The order isn’t put on hold, so pause delivery yourself if you need to.
Payments That May Need a Refund
A payment the order wasn’t waiting for never completes it. Examples are a second payment, one for another amount, one that arrives after the buyer switched payment method, or one refunded before your store confirmed it.
- It’s logged on the order and listed in the admin notice Payments that may need a refund, with its payment ID.
- An unpaid order goes on hold, and no new Revolut payment or saved-card charge starts for it while the payment is listed.
- Refund it in Revolut. One refund of the whole listed amount clears the notice once its webhook arrives. You can also click Mark as handled. Either way, that payment never pays the order, and the order’s status stays as it is.
- A renewal with such a payment isn’t charged to the saved card again automatically, even after you clear it. The customer can pay it by link.
Currencies
Revolut (Stackless) charges in 21 currencies: AUD, CAD, CHF, CZK, DKK, EUR, GBP, HKD, HUF, ILS, JPY, MXN, NOK, NZD, PLN, RON, SEK, SGD, TRY, USD and ZAR. It’s hidden in any other. Yen amounts are rounded to whole yen.
With Multi-Currency Checkout, tick Revolut under Payment gateway routing in each currency that has a saved gateway list. INR, USD, EUR and GBP start with a fixed gateway list that doesn’t include it.
What Data Is Sent
- With each payment: the amount, currency, order number, internal order and payment references, your store’s name, the return address on your site and the buyer’s name and email.
- When a card is saved: a Revolut customer is created with the buyer’s name and email. Revolut’s window also gets the billing address, when there’s a country and postcode, and the language.
- With a refund: the amount, currency, references and the reason you typed.
- For setup: your webhook URL. API requests also carry your key and the plugin’s name and version.
- Kept on your site: Revolut’s references, a hashed buyer identifier and, for saved cards, the brand, last four digits and expiry. Card numbers go straight to Revolut.
Stackless adds suggested Revolut wording to the WordPress privacy policy guide.
Limits
- The gateway hasn’t taken a sandbox or real Revolut payment, so test a payment, a refund and a renewal on your own account first.
- On localhost or an IP address, Revolut’s hosted page can’t send the buyer back to your site.
- Revolut can’t be duplicated for a second account.
- A subscription another provider bills on its own schedule can’t be moved to Revolut by paying with it.
- A subscription that a recurring coupon makes free doesn’t show Revolut at checkout.
- There’s no page for customers to change a saved card. When they pay an auto-charged renewal by link, that card replaces the saved one.
- On copies of the live store, saved cards aren’t charged and refunds aren’t sent. A shopper who checks out on a copy that has live keys is still charged, so use test mode there.
For Developers
| Hook | Type | Use |
|---|---|---|
gtfc/revolut/settings | filter | The gateway’s settings when they load: ($settings). |
gtfc/revolut/webhook | action | Runs after a verified event is applied: ($type, $id, $mode, $outcome). |