How ZyndPay works: money in, ledger, escrow and money out

Merchant payments: an order becomes a tracked payment

A merchant starts with an order or invoice reference, then creates a payment through a link, hosted checkout or the approved API flow. The buyer sees only the methods enabled for that account and context—such as a supported stablecoin-network pair, card or mobile money where available.

The browser return is not the accounting event. ZyndPay tracks the external rail asynchronously and exposes authoritative state through authenticated product surfaces and signed events. The merchant consumes those states idempotently and fulfils only under its confirmed-payment policy.

The ledger keeps economic movements balanced

ZyndPay represents money movement in balanced double-entry records. A payment received, fee, refund, conversion, hold, payout or P2P release is not a direct balance edit; it has a corresponding economic entry. This makes transaction history and balance explanation part of the same model.

External payment status and internal ledger status remain distinct. A provider callback, blockchain observation or payout acceptance must be reconciled before the platform describes value as settled or delivered. That separation is essential when a rail is delayed or sends duplicate notifications.

The consumer wallet is custodial

In the consumer app, ZyndPay controls the on-chain keys for the account balance. Users sign in and authorize instructions with the account controls provided; they do not receive a seed phrase for that ZyndPay balance. The available balance is derived from recorded state and reduced by any valid holds.

Custodial does not mean bank deposit. ZyndPay is not a bank, the balance is not deposit-insured and stablecoins retain issuer, peg, network and liquidity risks. Users should protect account access and verify the exact asset, network and destination shown before authorizing a blockchain action.

P2P reserves the crypto leg in escrow

A P2P seller offers stablecoins for local-money payment. When an order starts, ZyndPay reserves the seller’s crypto amount inside the custodial ledger so it cannot be spent twice. The buyer then pays the seller using the verified-name method shown for the order.

The seller verifies actual receipt before release. If the order completes, the reserved crypto moves to the buyer; if it is validly cancelled or resolved otherwise, the reserve returns under the order rules. Proof uploads, timers, chat, reputation and dispute review support the decision but do not make a forged receipt true.

Money out is an instruction, review and final rail state

Merchant payouts and consumer withdrawals follow the enabled destination path. Applicable identity, beneficiary, sanctions, AML, balance and blockchain-risk checks precede approval, and risk-based policy can hold a request for human review.

Accepted, approved, processing and completed are distinct. Only the terminal rail evidence supports saying that the destination received funds. Account-specific pricing, limits, settlement timing and availability are shown before live processing rather than published as one universal promise.

FAQ

Does ZyndPay put every money movement on a blockchain?

No. Merchant and consumer economic state is recorded in ZyndPay’s ledger. P2P escrow is an internal custodial reservation; blockchain interaction is used only where the enabled external flow requires it.

Who controls the consumer wallet keys?

ZyndPay controls on-chain key operations for the custodial consumer wallet. Users authorize actions through their accounts rather than holding a ZyndPay seed phrase.

How does P2P escrow protect an order?

The seller’s crypto is reserved in the custodial ledger during the trade, so it cannot be spent elsewhere. Release follows verified receipt and the order or dispute process.

When is a payout complete?

Only when the destination rail reaches its terminal completed state. Accepted, approved and processing are earlier states and must not be presented as delivery.