H2H Integration (White Label)

Learn how to enable Host2Host (H2H) — white-label crypto payment acceptance without redirects: payment details are displayed in your interface, and statuses are delivered via API.

Host2Host (H2H) is a white-label API integration scenario in which payment details are transmitted directly to your side without redirecting the user to the CryptoCloud payment page. You fully control the payment interface: you display the wallet address, network, and amount within your website or application design, maintaining a consistent branded user experience.

Payment statuses are delivered via API notifications and can be processed automatically in your system.

When to use H2H:

  • White-label crypto payment acceptance is required without mentioning the payment provider

  • Redirects to external pages are prohibited

  • Full control over the payment UI/UX is needed

  • A custom checkout, application, or terminal is used

How H2H works

  1. Request authentication All API requests are signed with your API keys from the CryptoCloud project settings.

  2. Invoice creation You send an API request to create an invoice, specifying:

  • invoice amount

  • invoice currency

  • cryptocurrency parameter — the currency in which the user will pay

In H2H, specifying cryptocurrency is mandatory, as the payment details are generated for the selected currency.

  1. Receiving payment details The API response returns:

  • unique wallet address

  • exact payment amount

You display this data to the user in your interface (white-label checkout).

  1. User payment The user transfers funds to the issued address in the specified network and amount.

  2. Payment notification (Postback) After funds are received, CryptoCloud sends a POST notification to the notification URL configured in your project settingsarrow-up-right. You verify the notification signature and update the order/service status in your system.

  3. Invoice status check (optional) The invoice statusarrow-up-right can be requested manually via API using the INV number. Used for reconciliation, rechecks in case of notification failures, or manual processing.

Integration result

After H2H is enabled:

  • payments occur in a fully white-label interface

  • the user does not leave your website or application

  • the CryptoCloud brand is not shown during payment

  • payment statuses are automatically synchronized via API

Important

  • the user must pay strictly in the specified network and currency

  • the amount must match the API-issued amount

  • each invoice has a unique address

  • the address is valid for one invoice only

Connection

The technical description of invoice creation, status checks, and Postback handling is available in the API Reference V2 sectionarrow-up-right.

Last updated

Was this helpful?