Fund flow transparency

How EcomTrade24 Pay handles merchant funds and payout questions.

EcomTrade24 Pay is built as a checkout, routing and merchant operations layer. Every real payment should be traceable through a session, merchant account, provider route, payment status, ledger record and, where applicable, a wallet or blockchain transaction reference.

Request payout check Open Trust Center Acceptable Use

Gateway, not a vague balance box

A checkout session is tied to a merchant, amount, currency, route and status so the payment path can be reviewed instead of guessed.

Fees must be visible

Platform fees and routing costs should be explainable from the session, plan and provider path. Hidden manual deductions are not the operating model.

Claims need references

A public claim without a session ID, order ID, wallet address or merchant email cannot be verified. Real cases can be investigated.

What is normally logged around a payment?

Session record

Session ID, merchant account, amount, currency, customer email where required, success/cancel URLs and webhook target.

Routing record

The selected checkout route or provider path used for the handoff. Merchant plans and method availability can affect this route.

Payment status

Created, redirected, awaiting payment, paid, failed, expired, manual review or settlement-related states depending on the flow.

Provider / chain references

Provider payment IDs, callback payloads, transaction hashes or wallet references where the selected route provides them.

Merchant ledger effect

The final amount, platform fee logic and payout/settlement state should be traceable from the merchant account.

Why a payout can look delayed

The buyer started a session but never completed the provider payment.

The provider status has not reached a final paid/finished state yet.

A webhook or callback arrived late, failed, or needs reconciliation.

A wallet address, domain, customer email or merchant setup value is missing.

A route requires manual review because the paid asset, amount or country signal does not match expectations.

The provider or blockchain transaction exists, but the merchant dashboard needs a settlement rescan.

A payout investigation is strongest when it includes a session ID, order ID, merchant email and wallet address. Without at least one concrete reference, nobody can verify the claim responsibly.

Investigation path

If a merchant believes money is missing, the next step is evidence, not public guessing.

We review the payment path by checking the session, route, provider status, callback history, wallet reference and merchant ledger. Unsupported public claims without transaction details cannot be confirmed or denied responsibly.

1. Submit references

Send merchant email plus session ID, order ID, wallet address or shop URL.

2. Match the route

We identify the route/provider path and expected settlement behavior.

3. Check status evidence

We compare dashboard status, provider callbacks and wallet/chain references.

4. Resolve or explain

The result should be a clear status update, correction, rescan or explanation.

Need a payment or payout checked?

Use the public payout check form with the references you have. This is the clean way to turn a claim into an auditable support case.

Open payout check