Overview
The HostToHost mode allows merchants to receive payment details directly from the payment gateway without redirecting to our checkout page. This feature enables merchants to implement their own payment processing flow, providing greater flexibility and customization in handling payments. When HostToHost mode is enabled, the API will return payment details specific to the chosen payment method.
| Payment Method | Supported | Response Structure |
|---|---|---|
| CRYPTO | ✅ Yes | Returns a payment address and network |
| CARD | ❌ No | Will release in Q1-2025 |
| SKRILL | ✅ Yes | Returns a payment link |
Enabling HostToHost Mode
To enable HostToHost mode, include the host_to_host_mode field set to true in your API request when creating an invoice. By default, this field is set tofalse, which merchant should redirect to our checkout page via invoice_url.
When HostToHost mode is enabled, different payment methods may require specific request parameters and will return varying response structures in field host_to_host_data. Below, we outline the required parameters and response formats for each supported payment method.
Crypto Payments
When using cryptocurrencies, the following parameters are required in addition to the standard invoice parameters:
| network | Specifies the blockchain network the buyer will use to make the payment. See Supported Networks. |
| pay_currency | Defines the cryptocurrency in which the buyer will make the payment (e.g., BTC, ETH, USDT, USDC). |
The response will include a payment address and the network to be paid.
Example Response:
{
"network": "NETWORK_ETH",
"address": "0x1f5f7104a57da3b18a51660e6e1310e56b6318d3",
"pay_currency": "USDT",
"pay_amount": 20.38,
"type": "CRYPTO"
}
Skrill Payments
For Skrill payments, the response will return a payment link that the merchant can provide directly to the customer.
Example Response:
{
"url": "https://api.test.paysafe.com/alternatepayments/v1/redirect?accountId=1002759750&paymentHandleId=f1d1c806-bb19-496a-b1cc-6eed4f860af8&token=eyJhbGciOiJIUzI1NiJ9.eyJhY2QiOiIxMDAyNzU5NzUwIiwicHlkIjoiZjFkMWM4MDYtYmIxOS00OTZhLWIxY2MtNmVlZDRmODYwYWY4IiwiZXhwIjoxNzI0MjE1NTUyfQ.tnFlups-ft_wZeOEAzE9Y7OsVXebbD061nGfWtDZR3o",
"type": "SKRILL"
}
Handling Payment Status
In HostToHost mode, you should implement a webhook listener at the URL specified in the notify_url parameter. The gateway will send notifications about the payment status to this URL, allowing you to update the order status in your system accordingly.
Use Cases
HostToHost mode is ideal for merchants who:
Want to maintain full control over the payment experience.
Need to integrate the payment process into their existing custom workflows.
Prefer to bypass the standard checkout page to create a seamless customer experience.
Conclusion
HostToHost mode provides the flexibility needed to manage payments directly within your own systems. By using this mode, merchants can leverage customized payment processes while still benefiting from the security and reliability of our payment gateway.