ScanPay review

ScanPay is an API-first payment gateway and payment service provider for online merchants and developers. The product information describes it as acquirer-agnostic and based in Aarhus, Denmark. It handles card and mobile payments, recurring billing, refunds, voids, and other transaction actions. Merchants can use a hosted checkout, or connect through the API.

The checkout supports modern browsers, detects language automatically, and can send payment links by SMS or email. For integrations, ScanPay uses HMAC-SHA256 callbacks and sequential pull requests to keep transaction states in sync and help prevent duplicate captures. Its recurring-billing functions can register subscribers, charge repeat payments, and issue renewal links when a card expires.

The stated pricing is pay as you go: 0.25 DKK per transaction, with no monthly subscription or setup fee. That is a useful starting point, but the published pricing information alongside it is inconsistent, so merchants should confirm the actual rate in writing before budgeting around it.

The clearest advantage is the breadth of payment operations in one gateway. The feature list covers authorization, automatic or manual capture, refunds, and voids, alongside recurring charges. That may suit a merchant that needs more than a checkout form and wants transaction actions available through an API.

ScanPay also describes multi-acquirer routing, including automatic failover. For merchants using multiple acquiring banks, that is a relevant capability to assess; the available information does not name supported acquirers or explain how routing rules are configured. The dashboard adds real-time transaction tracking and role-based team permissions, while callbacks and sequential pull requests provide two ways to keep transaction records aligned.

Other useful details in the listed feature set include:

• Hosted checkout with automatic language detection and payment links by SMS or email.
• Recurring billing tools for subscriber registration, repeat charges, and card-expiry renewal links.
• No monthly subscription or setup fee in the stated pay-as-you-go model.

Those features make ScanPay worth a closer look for API-led businesses. They do not, by themselves, establish which payment methods, markets, or acquiring partners a particular merchant can use.

The biggest issue is pricing clarity. The product information says 0.25 DKK per transaction, but the published pricing record lists Basic, Field Serve Lite, and Field Serve Plus plans, with monthly prices of $0, $30, and $99.99. It also lists field-service add-ons and card-processing rates. Those details do not clearly describe this payment gateway, so we would not treat them as ScanPay fees. Get a written quote that confirms transaction charges, acquiring costs, and any other fees.

The available information does not publish a transaction-volume cap, supported countries or currencies, named acquiring banks, or limits on payment methods. It also does not specify dispute fees, service-level commitments, support terms, or the conditions that trigger automatic failover. Merchants evaluating a switch should ask for those details before moving recurring billing or routing live payments.

The listed 0.25 DKK rate is useful as an indication, not enough for a cost comparison without the full fee schedule. The Reddit threads we read concern other projects also called ScanPay, not this Aarhus-based gateway, so they do not fill in those product or pricing gaps.

The ScanPay details published list pay-as-you-go pricing at 0.25 DKK per transaction, with no monthly subscription or setup fee. That is the relevant figure to verify with ScanPay before budgeting; the source does not say whether other charges apply or spell out processing rates.

There is a pricing mismatch in the published material: a separate plan table lists Basic at $0 per month, Field Serve Lite at $30 per month and Field Serve Plus at $99.99 per month. It also lists Field Serve add-ons, including estimates for $9.99 per month and online card processing at 2.7% + $0.20. Those plan names and charges do not match ScanPay, so we would not treat them as ScanPay prices. Annual prices for those plans are not published, either.

Before switching, ask for a written quote covering transaction fees, acquiring-bank charges, refunds, recurring payments and any other costs. The published material does not confirm ScanPay’s processing rates or support terms.

Switching to ScanPay is likely to involve more than replacing a checkout form. Its listed features include hosted checkout, payment links, recurring billing, HMAC-SHA256 callbacks, transaction-state synchronization and multi-acquirer routing. A migration plan should account for how your current system creates payments, handles callbacks, captures or refunds transactions, and tracks recurring charges. Those are practical areas to map, not published migration instructions.

The published material does not state whether ScanPay can import stored payment credentials or subscriptions, or what data export is available if you leave. Confirm both before moving recurring billing or relying on the dashboard as your transaction record. We also have no Reddit posts or comments in the published material, so we can’t responsibly say what users report as common reasons for leaving ScanPay. Get written answers on export, support and fees, and test the cutover plan against your existing payment flows before committing.