Fund flow transparency

How provider payments and non-custodial merchant settlement work.

EcomTrade24 Pay is a technical checkout, routing and merchant-operations layer. The selected independent provider performs customer KYC and payment-method execution. EcomTrade24 records the session and, where V3 is enabled for the route, detects the resulting blockchain asset and triggers an immutable contract split without a session private key.

Request payout check Open Trust Center Acceptable Use

Software session, not an investment account

A checkout session is tied to a merchant sale, amount, currency, route and status. It is not a trading account, investment deposit or promised-return product.

Immutable V3 fee rule

For Non-Custodial Settlement V3, the fee ratio and both destinations are fixed in the session contract before the address is funded.

Fixed merchant destination

Merchant assets accumulate in a chain-specific vault that can release only to the merchant wallet fixed at vault creation.

External payment provider

Customer payment processing is performed outside EcomTrade24.

The selected provider accepts or rejects the customer, performs required KYC/AML checks, processes the card, bank or alternative payment method and executes provider-side conversion under its own terms.

Non-Custodial Settlement V3

One deterministic address, no session private key.

Where V3 is enabled, the same checkout address is watched on Polygon and Ethereum. When POL, ETH, supported USDC or USDT arrives, the immutable contract sends the fixed fee share to the platform wallet and the merchant share to the correct chain-specific merchant vault.

Read full role disclosure

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.

Contract settlement evidence

For V3, the predicted address, detected chain and asset, funding hash, immutable fee ratio, session settlement hash and merchant-vault address are recorded.

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 independent provider, selected method and expected technical handoff.

3. Check chain evidence

We compare provider callbacks, Alchemy events, chain confirmations, contract deployment and settlement hashes.

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