Skip to main content

Aggregated Payment (Merchant Collection by Card Number)

This transaction type enables a payment service Aggregator to accept customer payments on behalf of an integrated Merchant. Funds are debited from the Payer and distributed between the Merchant (net of the Aggregator fee) and the Aggregator (fee portion) automatically.

Business Flow

  1. Merchant signs an agreement / onboards with the Aggregator.
  2. Aggregator instructs the Merchant to create (or provide) a wallet in the heth.me system and sends back the wallet_id.
  3. Using its own API key, the Aggregator creates a payment transaction specifying the Merchant wallet details in money_storage_merchant and the Payer card details in money_storage.
  4. Upon successful processing, the balances of the Payer, Merchant, and Aggregator are updated in a single step.
  5. The transaction status can be polled using the standard transaction retrieval method (authorized with the same API key).

Example Request

curl --location --request POST 'https://app.heth.me/api/v1/transactions' \
--header 'Content-Type: application/json' \
--header 'x-api-key: 165f15d4-0143-4d6a-a387-e3c44aaef7f6' \
--data '{
"params": {
"amount": 10000000000000000,
"currency": "USDT",
"env": "prod",
"type": "payment",
"route": "hot_hot_ETH",
"money_storage_merchant": {
"wallet_id": "002305DDA4FED2BABA57C1C70CC8E575D5D8A7AD",
"network": "ETH",
"type": "p2p_proxy",
"currency": "USDT"
},
"money_storage": {
"network": "ETH",
"type": "bank_card",
"currency": "USDT",
"cardnumber": "9981040364688168",
"cvv": "128",
"exp_month": "08",
"exp_year": "2026",
"cardholder": "John Doe"
},
"description": "Payment",
"txid": "hot_hot_ETH"
}
}'

Field Reference

FieldDescriptionTypeExample
amountTransaction amount (minor units)Number10000000000000000000
currencyTransaction currency (default USDT)StringUSDT
envExecution environment (default prod)Stringprod
typeTransaction type (payment)Stringpayment
routeProcessing route (must match configured mapping)Stringhot_hot_ETH
money_storage_merchantMerchant (payee) wallet descriptorObject
> wallet_idMerchant wallet identifierString002305DDA4FED2BABA57C1C70CC8E575D5D8A7AD
> networkBlockchain network (TRX or ETH)StringETH
> typeWallet interaction type (e.g. p2p_proxy)Stringp2p_proxy
> currencyMerchant settlement currency (default USDT)StringUSDT
money_storagePayer funding instrument descriptorObject
> networkBlockchain network (TRX or ETH)StringETH
> typeInstrument type (bank_card)Stringbank_card
> currencyPayer currency (default USDT)StringUSDT
> cardnumberVirtual card numberString9981040364688168
> cvvVirtual card CVVString128
> exp_monthCard expiry monthString08
> exp_yearCard expiry yearString2026
> cardholderCardholder nameStringJohn Doe
descriptionHuman-readable descriptionStringPayment
txidClient-side transaction identifierStringhot_hot_ETH

Notes

  • The Aggregator fee logic is applied automatically based on the API key configuration.
  • Ensure route matches an enabled processing route for the provided API key.
  • Use idempotent txid values to avoid accidental duplicate submissions.
  • Retrieve transaction status via the standard GET transaction endpoint (polling until a terminal state is reached).