For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
RegisterLoginSandbox Login
GuidesRecipesAPI Reference
GuidesRecipesAPI Reference
  • Getting Started
    • Getting Started with Checkout
    • ACH Checkout
    • Card Checkout with Credits
    • Card Checkout
    • Direct USDC Settlement
    • Fiat/Crypto Pay-ins
    • Secure Marketplace Checkout
    • EVM Checkout
    • How to Enable Checkout with Credit Cards
    • Quick Start Marketplace Implementation
    • Payouts
    • Common FAQs
  • Checkout
    • Settlement Locations
      • Settlement to Coinflow Wallet
      • Merchant BYO Wallet Settlement
      • EVM Transactions In-Depth
        • Whitelist Your Contracts
          • Implement Settlement to EVM Contract
          • How EVM Transactions Work
          • Tempo Signature Integration (secp256k1 / P-256 / WebAuthn / Keychain V2)
    • Checkout Webhooks
  • Payouts
    • Payout Overview
    • What is a Payout
  • Subscriptions
    • Subscriptions Overview
  • Marketplaces
    • Marketplace Overview
    • How Marketplaces Work
    • How to Withdraw USDC
    • Countries Eligible for USDC Withdraw
    • Marketplaces Webhooks
    • Marketplaces Implementation
  • Developer Resources
    • Custom Branding
    • Checkout Implementation
    • Webhooks
  • Merchant Dashboard
    • Login & Account Access
    • Users and Roles
    • Rate Limits
    • Developer Contact
LogoLogo
RegisterLoginSandbox Login
On this page
  • How Coinflow EVM transactions work
  • How to debug EVM transactions
  • Steps to debug
CheckoutSettlement LocationsSettlement to ContractsSettle to EVM Contract

EVM Transactions In-Depth

Was this page helpful?
Previous

Tempo Signature Integration (secp256k1 / P-256 / WebAuthn / Keychain V2)

Accept Tempo wallets signing with secp256k1, raw P-256, WebAuthn passkeys, or Keychain V2 access-key envelopes for EVM credits redemption on the Tempo chain.

Next
Built with

How Coinflow EVM transactions work

  1. User enters card info
  2. Card gets authorized + passes chargeback checks
  3. Coinflow runs transaction

At this point, Coinflow contract has a USDC balance that can be deducted from to send USDC to the merchant for settlement. Coinflow contract receives:

  • The amount of USDC to approve
  • Merchant contract address
  • Function call data (aka the data to call the merchant contract with)
  1. Coinflow contract calls approve() on the USDC contract, allowing a merchant’s contract to pull $X amount of USDC from coinflows contract.
  2. Coinflow’s contract calls the merchant’s contract with their provided function call data.
    • Inside the merchants contract, a call to the USDC contract transferFrom() function is made. This takes in merchants’ contract address, the amount of USDC to transfer, and the destination that will receive USDC (destination could be end-user wallet/ merchant wallets/ merchant contract). This represents fulfillment of payment or settlement.
    • Then, inside the function data passed to the Coinflow contract, the merchant needs to include the end users wallet address so that the merchants contract can send the NFT to the end user.

How to debug EVM transactions

When merchants submit transaction data, Coinflow simulates it upfront to ensure successful execution. The response includes any revert reasons and the corresponding transaction data. Receiving an error message INSUFFICIENT FUNDS TO REDEEM indicates the transaction failed due to inadequate funds.

Steps to debug

  1. Check response details
    • Look for the revertReason messages to understand why the transaction failed.
    • Identify which addresses (to and from) are involved in the failure.
  2. Use a transaction simulator tool like Tenderly
  • Copy the transaction data into a simulation tool like Tenderly for more detailed reasons of where the transaction failed
  1. Analyze transaction data
  • Verify the to field in the transaction data matches the Coinflow contract
  • Ensure the from field correctly corresponds to the wallet paying USDC