Skip to content
The ValyrPayMerchant Services

Service

A gateway built for merchants with more than one acquirer.

When your business needs a gateway, we give you access to ValyrPay’s: one API for one-off payments and subscriptions, with hosted checkout, Apple Pay, routing and dispute tools built in.

Operated by
ValyrPay, of which we are part.
Payments
One-off card payments, Apple Pay and subscriptions on one API.
Acquirers
Built for multi-acquirer set-ups, with routing across the acquirers your account uses.
Disputes
Visa Verifi: Order Insight, Rapid Dispute Resolution, Compelling Evidence 3.0.

Who it is for

For merchants whose payments have outgrown one provider.

A gateway is worth changing for when it removes a dependency, a second integration or a manual process. These are the cases where it does.

  • More than one acquirerYour acquiring relationships behind one checkout, with routing between them.
  • Subscription businessesPlans, trials and renewals on the same API as one-off payments — no second billing system.
  • Cards on file that must moveStored cards that stay usable when you add or change an acquirer.
  • Engineering teamsA clean, versioned API with idempotency, signed webhooks and a sandbox.
  • Merchants watching disputesVerifi’s pre-dispute services answered from the gateway’s own payment records.
  • A smaller card-data footprintHosted checkout, so card numbers never touch your servers.

What you get

Checkout, billing and risk on one integration.

Each of these is live on the ValyrPay gateway today.

One API

Payments and subscriptions through one versioned API, with idempotency keys on every money-moving request and signed webhooks for every lifecycle event.

Routing across acquirers

Each payment routed by card, issuer country and amount; a soft decline or a provider error can fall through to the next eligible acquirer.

Checkout

A hosted payment page for every payment, an embeddable form for your own page, Apple Pay in both, and 3-D Secure handled for you.

A card vault that stays yours

Store a card once and charge it through any connected acquirer. Your systems hold a token; agreements on file move with you between acquirers.

Subscriptions

Plans, prices, trials, pauses and cancellations, terms fixed at sign-up, and failed renewals retried on schedules chosen by the decline code.

Fraud and disputes

Velocity limits, blocklists and rules you control; Verifi’s pre-dispute services; and an evidence pack for every dispute worth contesting.

The technical sheet

What your developers will find.

The gateway is built and operated by ValyrPay. Its API, documentation, sandbox and pricing are ValyrPay’s; we help you decide whether it fits and, if it does, get you connected.

We are part of ValyrPay, and we say so whenever a recommendation is for a ValyrPay service. Where the gateway does not fit your business, we will not push it.

API
One versioned REST API for payments and subscriptions, JSON over HTTPS, authenticated with an API key.
Amounts
Integers in minor units with an explicit currency — never a floating-point number.
Safety
An idempotency key on every request that moves money, so a retry never charges twice.
Webhooks
Signed events for payments, subscriptions and disputes.
Checkout
A hosted page for every payment, or an embeddable form; Apple Pay in both.
Authentication
3-D Secure handled by the gateway, set per payment or per account.
Acquirers
One integration in front of the acquirers your account uses, with routing between them.
Testing
A sandbox first, then live on the same integration.

How it works

From a fit check to your first live payment.

  1. Fit check

    Your acquirers, markets, volumes and model. If the gateway does not fit, we say so here.
  2. An acquirer

    Payments are acquired by an acquirer the gateway connects to. If you need one, we can introduce you.
  3. Sandbox

    Your developers build against the sandbox with test cards and webhooks.
  4. Live

    Live keys on the same integration, once the acquirer has boarded your account.
  5. Grow

    Add acquirers, routing rules, subscriptions and Verifi services as you need them.

Before you start

What we need, and what we cannot do.

What we need from you

A gateway connects a business to its acquirers, so we start with both.

  • Your acquiringYour current acquirers and merchant accounts — or our help finding one.
  • Your modelOne-off payments, subscriptions or both; markets, currencies and expected volumes.
  • A technical contactSomeone who will own the integration and its webhooks.
  • Your checkoutWhere payments happen today: your site, an app, a hosted page.

What this service does not do

A gateway is one part of accepting payments. These parts stay with others.

  • It is not an acquirer. Your merchant agreement, and the decision to accept you, are the acquirer’s.
  • It does not hold your money. Settlement is paid by your acquirer; the gateway reconciles it.
  • It works only with acquirers it is connected to. If yours is not, we tell you before you build.
  • Routing cannot rescue a payment the card issuer refuses. It helps where another acquirer may approve, not where the card is declined.
  • We do not set its prices. ValyrPay quotes them before you sign.

Questions

Asked before we start.

If yours is not here, ask us — or read the full list.

All questions

Who runs the gateway?

ValyrPay, which builds and operates it. The ValyrPay Merchant Services is part of ValyrPay. We help you decide whether the gateway fits and get you connected; your gateway agreement is with ValyrPay.

Do I need a new merchant account?

You need a merchant account with an acquirer the gateway connects to. If you already have one with a connected acquirer, it can be used; if not, we can introduce you to one where your business fits.

Can I keep my other provider?

Yes. Many merchants run more than one acquirer for resilience. The gateway routes your payments across the acquirers your account uses; payments through other providers stay where they are.

Does it support subscriptions?

Yes, on the same API as one-off payments: plans, prices, trials, pauses and cancellations, with terms fixed for the life of each agreement and failed renewals retried on schedules chosen by the decline code.

Is there a sandbox?

Yes. Your developers build and test against the sandbox first, then go live on the same integration with live keys.

See whether the gateway fits your business.

Tell us about your business in a short form, or write to applications@thevpms.com. A person reads every enquiry and replies.