PAYMENT INFRASTRUCTURE / ONLINE PAYMENTS
Payment gateway for reliable online payments
FoxPay combines hosted checkout, an embeddable payment frame and several payment methods: Open Banking, QR Pay, cards, Pay by phone and PayPal. Merchant availability depends on the business model, bank or provider connection and approval. Signed webhooks connect payments with orders.
- Product status checked
- 16 September 2026
- Reviewed by
- FoxPay product documentation
01Checkout
A payment surface designed to fit the store.
The gateway separates buyer-facing UI from server-side payment logic. Merchants can choose the integration path that fits their commerce stack, engineering resources and desired level of control.
Hosted checkout
FoxPay hosts the payment interface and reduces the amount of checkout code maintained by the merchant.
Payment frame
Checkout V3 can be embedded on approved store domains. Enablement and allowed origins are configured for each store.
02Payment methods
More choice for merchants rejected by standard PSPs.
FoxPay combines bank-direct and traditional payment paths. Enablement depends on the business model, target market, risk profile and provider approval.
Open Banking
Buyers authorise a bank-direct payment through the intended banking flow.
QR Pay Autopilot
After activation and bank connection, matching incoming transfers are reconciled automatically. Confirmation depends on the actual bank credit and its retrieval.
Card payments
Visa and Mastercard are actively offered where merchant fit, documentation, risk and provider requirements align.
Pay by phone
Buyers pay through their mobile provider. Enablement depends on target market, offer, merchant fit and provider availability.
PayPal
Seller onboarding, checkout and refunds are integrated. Use requires an eligible business category, provider approval and a fully connected PayPal merchant account.
03Payment state
Order state follows backend truth—not the browser.
Redirects support the user journey. Fulfilment and finance rely on verified server states, idempotent events and traceable references.
Explicit states
Created, pending, paid, failed and expired are processed as controlled transitions.
Signed webhooks
Events are verified, persisted and applied to orders idempotently on the server.
Retry behaviour
Temporary delivery failures can be retried without running the same business action twice.
Reconciliation
Payment, order and settlement references remain separately traceable for support and finance.
04Integration
From plugins to a custom REST integration.
REST API
Custom systems create payments on the server and process signed webhooks. Additional merchant polling access requires separate enablement.
WooCommerce
The plugin connects checkout, orders and payment status without a bespoke shop integration.
Shopify
A manual Shopify payment method triggers an emailed payment link after the order is placed. A custom app and order webhooks connect the store to FoxPay.
JTL
The plugin, hosted checkout and signed status webhooks are implemented. Sandbox component flows are tested; the full storefront checkout remains part of individual acceptance.
04Workflow
From merchant scope to a production gateway
The exact sequence depends on the business model, payment paths and commerce system.
- 01
Define scope
Document the merchant case, countries, payment paths and checkout variant.
- 02
Set up access
Prepare API access, the webhook endpoint and a separated test configuration.
- 03
Test the happy path
Create and authorise a payment, then map the confirmed status to the order.
- 04
Test failure paths
Cover cancellation, expiry, late confirmation, duplicates and redelivery.
- 05
Control go-live
Activate the approved merchant scope and operate monitoring and reconciliation.
05Evidence
Integration paths at a glance
The choice depends on the commerce system, desired control and operating model.
| Path | Best suited to | Operating focus |
|---|---|---|
| Hosted checkout | Fast, clearly bounded integration | Redirect and backend status |
| Payment frame | Embedded checkout experience | Embedding and status |
| REST API | Custom commerce and platform flows | Webhooks and idempotency |
| Plugin | Supported commerce platforms | Order status and updates |
Availability of individual payment paths and integrations depends on current product status and the reviewed merchant scope.
06FAQ
Frequently asked questions
Answers for the current, expert-reviewed scope.
Which checkout variants does FoxPay support?
FoxPay supports a hosted checkout and an embeddable payment frame. The right path depends on the commerce platform and desired integration scope.
When may an order be treated as paid?
Fulfilment should rely on a server-confirmed payment state. A browser redirect alone is not sufficient.
Which payment paths are currently relevant?
Open Banking, QR Pay, cards, Pay by phone and PayPal are technically integrated. Methods are approved per merchant, market and provider. PayPal requires an eligible business category and a fully connected seller account.
Can the gateway be integrated without a plugin?
Yes. Custom systems can use the documented REST API and webhooks. API keys and webhook secrets must remain in server-side systems.