timeline
field on the Charge represents where the payment is in the Commerce flow. For a completed transaction this looks like:
payments
field. This is similar to:
transaction_id
field represents the hash of the transaction that can be used to find it onchain. Payments can happen on Eth Mainnet, Polygon, or Base, so you must refer to the network
field to successfully locate the transaction.
Network | Chain ID | Block Explorer Link |
---|---|---|
Ethereum Mainnet | 1 | https://etherscan.io/tx/<tx_hash> |
Polygon Mainnet | 137 | https://polygonscan.com/tx/<tx_hash> |
Base | 8453 | https://basescan.org/tx/<tx_hash> |
addresses
, and no longer use the pricing
field’s entries for individual crypto currencies.
addresses
, the typical use case was locating an onchain transaction, which can be done following the guide above.pricing
, the typical use case was determining the amount received from the Payer.settlement_currency
field under pricing
to know exactly what you received.
COMPLETED
.
Additionally, you can use webhook events such as charge:confirmed
to get real-time updates when a charge is fully confirmed and finalized. That said, charge:pending
is enough to make a charge as paid, because it represents that the payment is confirmed by the respective chain.
charge:pending
is likely sufficient to consider a charge as paid, be aware that a blockchain reorganization (reorg) could result in a loss of funds. It might be safer to wait for the charge:confirmed
status for final confirmation.<Checkout />
component provides a one-click checkout experience for onchain commerce, simplifying payment processing for developers. Key features include:
<Checkout />
component with minimal setup.chargeHandler
prop: