H2H processing

What H2H processing is

H2H (host-to-host) processing means the merchant or another PSP talks to the provider's server directly through an API, instead of redirecting the customer to a hosted payment page. The merchant draws its own checkout, sends the order to the provider, receives payment details (a card number, UPI ID, bank account, QR) or a status, and shows them in its own interface. In the P2P world, H2H is the standard way for a payment gateway to plug into a team's or trader network's liquidity.

Who uses host-to-host integration

• PSPs and aggregators that resell capacity of other providers under their own brand.
• Merchants with their own cashier — casinos, brokers, marketplaces that want full control of UX.
• P2P gateways connecting to P2P teams and traders for pay-in and payout flows.
• Banks and EMIs exchanging payment files and statuses with corporate clients (H2H banking).

H2H vs hosted payment page

• Control: H2H gives you the checkout design and the data; a hosted page is faster to launch.
• Compliance: for cards, H2H means you handle card data, so PCI DSS scope grows; for local methods and P2P this matters less.
• Conversion: fewer redirects usually mean fewer drop-offs, but you own retries and error handling.
• Effort: H2H needs callbacks, status polling, reconciliation and appeal handling on your side.

What to check with an H2H provider

• API documentation, sandbox, callback signatures, idempotency.
• Supported methods per GEO (UPI, SBP, C2C, bank transfer) and the share of successful deposits.
• Limits per order and per day, payout support on the same rails.
• Settlement currency and frequency, deposit or prepayment requirements.

Related hubs

P2P processing, P2P & H2H software, cashier and payment pages, aggregators & cascading. Use the Offers tab for published H2H terms or post a request with GEO, methods and expected volume.