Payment by Card Number

This transaction type allows initiating a payout using a wallet identifier (wallet_id).

Business Flow

1. The API key holder prepares payout details including the recipient wallet_id.
2. A payout transaction is created specifying the wallet in money_storage.
3. Upon successful processing, funds are transferred to the specified wallet.
4. The transaction status can be polled using the standard transaction retrieval method.

Example Request

curl --location 'https://app.heth.me/api/v1/transactions' \
    --header 'Content-Type: application/json' \
    --header 'x-api-key: 440944de-e5a4-6aab-9c57-3bf2e7282c64' \
    --data '{
        "params": {
            "amount": 10000000000000000,
            "currency": "USDT",
            "env": "prod",
            "type": "payout",
            "route": "hot_hot_ETH",
            "money_storage": {
                "network": "ETH",
                "type": "p2p_proxy",
                "currency": "USDT",
                "wallet_id": "9D0089A4A8024E4724D03D2E572EB53DDE850B99"
            },
            "description": "Payout",
            "txid": "hot_hot_ETH"
        }
    }'

Field Reference

Field	Description	Type	Example
amount	Transaction amount (minor units)	Number	10000000000000000
currency	Transaction currency (default USDT)	String	USDT
env	Execution environment (default prod)	String	prod
type	Transaction type (payout)	String	payout
route	Processing route (must match configured mapping)	String	hot_hot_ETH
money_storage	Recipient wallet descriptor	Object
>network	Blockchain network (TRX or ETH)	String	ETH
>type	Wallet interaction type (e.g. p2p_proxy)	String	p2p_proxy
>currency	Wallet currency (default USDT)	String	USDT
>wallet_id	Recipient wallet identifier	String	9D0089A4A8024E4724D03D2E572EB53DDE850B99
description	Human-readable description	String	Payout
txid	Client-side transaction identifier	String	hot_hot_ETH

Notes

• Use a unique (idempotent) txid value to avoid accidental duplicate submissions.
• Ensure route matches an enabled processing route for the provided API key.
• Retrieve transaction status via the standard GET transaction endpoint (polling until a terminal state is reached).