Payment Methods
INVO Network's hosted checkout system accepts all major payment methods worldwide. No integration complexity - we handle everything.
One Integration, All Payment Methods
Our hosted checkout automatically supports all major payment methods. No additional code, no extra integrations - it just works.
Credit & Debit Cards
- ✓ Visa
- ✓ Mastercard
- ✓ American Express
- ✓ Discover
- ✓ JCB
- ✓ Diners Club
Global Support
- ✓ Cards issued worldwide
- ✓ Charged in USD (no conversion fee from INVO)
- ✓ +1.5% on cards issued outside the US
- ✓ Other methods where eligible (below)
Security Features
- ✓ 3D Secure (3DS2)
- ✓ PCI DSS Level 1
- ✓ Fraud detection
- ✓ Risk scoring
- ✓ Encrypted storage
- ✓ Secure tokenization
The checkout page shows the INVO logo by default. Upload your game's own logo in the console to show it instead; see Use your own logo on checkout.
Advanced Features Included
Saved Cards
Players can securely save their payment methods for faster checkout on future purchases. INVO handles the tokenization, so card data never reaches your servers.
- • Fast repeat purchases with confirmation
- • Secure card tokenization
- • Player can manage saved cards
- • Automatic card updates
Saving a card also captures the cardholder's authorisation to charge it later without them present. This is the mandate that recurring billing requires. See Subscriptions.
A player can save a card without buying anything, and without going through checkout: see Saving a card without a purchase. Once they have one, a subscription created without an explicit card id picks it up automatically.
3D Secure Authentication
Built-in support for 3D Secure 2.0 provides enhanced security and reduces fraud while improving approval rates.
- • Automatic bank verification
- • Biometric authentication
- • Reduced chargebacks
- • SCA compliance (Europe)
Mobile Optimized
Checkout experience is fully optimized for mobile devices with responsive design and native mobile wallet support.
- • Apple Pay ready
- • Google Pay ready
- • Touch-friendly interface
- • Auto-fill card details
Regional Payment Methods
Hosted checkout for a coin purchase offers the payment methods INVO has enabled that are eligible for the buyer's location and a USD charge. Cards are always offered. Which other methods appear (wallets and local methods) depends on the buyer and can change over time, so do not promise a specific method to your players.
- • Card only: subscriptions (the card road) and saved-card setup use a card.
- • Storefronts: Steam and the game storefront rail use the storefront's own methods; see Steam Purchases.
Nothing to configure: eligible methods appear on the hosted page by themselves.
Which purchase call do I use?
Pick your integration by where your product lives. You never choose a payment processor yourself. INVO routes each purchase to the right methods automatically.
There are two ways to tell us where a purchase comes from. If your title ships on more than one storefront, use storefront keys. They are the newer and simpler of the two, and you stop thinking about rails entirely.
| Your product | rail | What you get |
|---|---|---|
| A platform or non-game app (web / mobile storefront, creator platform) | "platform" | Cards + regional methods worldwide. This is the default if you omit rail. |
| A game distributed anywhere except Steam (mobile, standalone, web, console store) | "game" | Broad global & regional payment methods tuned for games. |
| A game distributed on Steam | "steam" | Players pay with their Steam Wallet (required for Steam titles). Use the in-client flow in the Steam purchase guide. |
"rail": "game" (or "platform" / "steam") to your purchase request body. Omit it and the rail comes from your storefront key's channel, then from the default payment rail set on your title, then "platform". Every webhook you receive echoes the rail back, so you always know which path a purchase took.rail out. The key already says where the purchase came from, so we know the rail. On the direct route (/purchase-currency), sending a rail that disagrees with the key is refused with RAIL_CHANNEL_MISMATCH rather than silently overridden; hosted checkout does not run this check, so do not send a conflicting rail there either. We would rather tell you than quietly bill a player through a route you did not ask for. A rail that agrees is accepted and ignored.One title, several storefronts
Most titles do not live in one place. The same title ships on Steam, on iOS, on Android, and on the web. Each storefront pays differently.
So every title gets one SDK key per storefront, all valid at the same time. Your server uses the key that matches where the player is buying, and INVO routes the payment correctly. You do not set a rail, and you do not have to know which processor sits behind each one.
| Storefront key | Use it for purchases originating from |
|---|---|
| steam | Your Steam build. Steam titles must use the Steam purchase flow. |
| ios | Your iOS app |
| android | Your Android app |
| web | A browser build or a web shop |
| console | Console builds |
Why Our Payment System Matters
For Your Players
- ✓Fast Checkout:Most transactions complete in under 30 seconds
- ✓Trusted Security:Bank-level encryption visible in the checkout UI
- ✓Their Preferred Method:Multiple payment options increase conversion
For Your Business
- ✓Higher Conversion:More payment methods = more completed purchases
- ✓Lower Fraud:AI-powered fraud detection protects your revenue
- ✓Zero Maintenance:We handle updates, compliance, and new methods
Ready to Accept Payments?
Get started with INVO Network's hosted checkout. One integration gives you access to all payment methods worldwide.
Card data never touches your servers, so hosted checkout keeps you in the lightest PCI scope (SAQ-A)