Apple Pay & Google Pay
Accept wallets once. Route them to any processor.
Orchestrapay decrypts Apple Pay and Google Pay itself, so wallet payments follow your routing rules instead of being tied to one processor.
- Stripe
- Worldpay
- Authorize.net
- Mastercard Gateway
Why wallets through Orchestrapay
The wallet should not decide which processor gets the payment.
We decrypt the token
Orchestrapay verifies and decrypts Apple Pay and Google Pay tokens itself, instead of leaving it to one processor.
Route wallets like cards
Once decrypted, a wallet payment follows your routing rules, fallbacks included, like any card payment.
Switch processors, keep the wallets
Changing processor does not mean setting up Apple Pay and Google Pay again. The wallets stay connected to Orchestrapay.
One tap to pay
Customers pay with Face ID, Touch ID or a fingerprint on their own device. There is no card number to type.
Apple Pay merchant validation
We handle Apple Pay merchant validation, and check that each request really comes from Apple.
In the form and the SDK
Wallet buttons appear in the Orchestrapay payment form and the React SDK, next to the card form.
Decrypt, then route
Your processor does not have to support the wallet. We do.
Most setups tie Apple Pay and Google Pay to the processor that decrypts them. Orchestrapay decrypts the token itself, so the wallet stops deciding where the payment goes.
Customer confirms
Face ID, Touch ID or a fingerprint on the customer's own device. No card form to fill in.
Encrypted token
The wallet hands back a payment token encrypted for Orchestrapay, not for any one processor.
We open it
Apple Pay: signature check, key exchange, AES-256-GCM. Google Pay: ECv2. All on our side.
Same rules as cards
The card inside goes through your routing graph like any other card payment.
Charged where you choose
Sent to the processor your rules pick, with the wallet cryptogram where the processor takes it, as Stripe does.
How it works
From one tap to the right processor.
Show the buttons
The payment form or React SDK shows Apple Pay and Google Pay where the customer's device supports them.
Decrypt
The customer confirms on their device. Orchestrapay verifies and decrypts the wallet token.
Route
Your routing graph sends the payment to the right processor, and falls back to the next one if it declines.
Questions teams ask before they switch.
Any card processor you connect that accepts decrypted wallet payments. Because Orchestrapay decrypts the token, the payment reaches the processor as a card payment, and the wallet cryptogram is passed along where the processor takes it, as Stripe does.
Turn on wallets without picking a processor for them.
Tell us which processors you use today. We will check which ones can take wallet payments and show you what it costs.
- Apple Pay and Google Pay behind one integration
- Wallet payments routed like cards
- A transparent number before you sign anything