Merchant payment flow
- Create an order in the merchant system.
- Present the amount and a validated eCoin destination or payment request.
- Observe the submitted transaction through a trusted or independently verified network source.
- Match the transaction to the order.
- Wait for the protocol-defined finality state required by the merchant’s risk policy.
- Mark the order paid and store the transaction reference for reconciliation.
Payment requests
A production payment-request format has not been defined. A future standard should be versioned and able to communicate destination, amount, network, expiration when applicable, order metadata that does not compromise privacy, and integrity protection.
Do not treat observation as settlement
Seeing a transaction propagated is not the same as finalized settlement. Payment processors should consume an explicit transaction state and define the business action associated with each state.
Refunds
The base design should assume finalized peer-to-peer transactions are not silently reversed by a merchant. A refund should normally be represented as a new authorized transaction back to a validated destination. The final protocol specification will determine exact behavior.
Reconciliation
Store an internal order identifier alongside the network transaction identifier in the merchant database, not inside sensitive public data unless the protocol explicitly provides a privacy-safe metadata mechanism. Reconciliation systems should be able to re-derive payment status from network records.