Getting Started with Implementing Checkout

Getting Started with Rapid Checkout Integration

Merchants implementing checkout / pay-ins should determine which payment methods you want to support, settlement location, how you will identify the payers.

Payment Methods

Credit Cards, Debit Cards, Apple Pay, Google Pay Payments

Approvely supports various payment methods, including credit cards, debit cards, Apple Pay, and Google Pay. These payment methods are eligible for fraud protection coverage, including chargeback protection and 3D Secure (3DS). Approvely recommends first testing payments without fraud protection tools enabled, then upon successful testing, test payments with chargeback protection and 3DS enabled.

For merchants enabling chargeback protection, ensure you:

• Add the chargeback protection script to every page of your site (not just the payment page).
• Pass chargeback protection parameters (e.g., chargebackProtectionData) to Coinflow.

Testing 3DS

To enable 3D Secure (3DS) for credit card transactions, merchants must pass the authentication3DS parameters when processing payments. If a friction challenge is required (e.g., a user must complete payment authentication), merchants must implement a 3DS challenge modal in their UI.

Note: If you're using Coinflow's checkout link or SDKs, no additional implementation is needed—our pre-built UI handles 3DS challenges automatically.

For testing 3DS functionality in the sandbox environment, be sure to use 3DS-enabled test card numbers

ACH Payments

If you're implementing ACH payments, you'll need a bank authentication provider to allow payers to securely link their bank accounts. If you don’t have an existing bank authentication provider, you can use Approvely's UI for this process. Bank authentication is already included if you are implementing using Approvely's SDKs or Checkout link.

Crypto Payments

To enable crypto pay-ins, you must contact the Approvely team. Note that crypto pay-ins are only available through Approvely's SDKs or Checkout link only. Crypto pay-ins are not supported via the API.

Settlement Locations

To begin integrating checkout with Approvely, all merchants must first configure their settlement settings. This step is essential, as it ensures merchants can receive payments for successful transactions. Without configuring settlement settings, payment statuses will not reach the settled status, and Coinflow won't be able to transfer funds for final settlement. Merchants must specify the settlementType when sending requests to Coinflow checkout. The correct settlement type depends on the location where the funds will be settled.

Regardless of which payment method the payer pays with, Coinflow will always instantly settle USDC either to:

1. Coinflow In-App Wallet
2. BYO (Bring Your Own) Merchant Wallet on Supported Chain
3. Solana Contract or EVM Contract

Identifying Payers

Creating Session Keys for Non-Crypto Native Users

Approvely supports both crypto wallet users and those without crypto wallets. If your payers do not have a crypto wallet, you can create a session key using your customer identifier. This ID should be consistent with how you identify customers in your system.

Important: Session keys are valid for 24 hours. It's the merchant’s responsibility to refresh the session key after it expires.

Creating Session Keys for Crypto Native Users

If your payers already have a crypto wallet, you can use the wallet address to uniquely identify the payer when interacting with Coinflow. Coinflow is wallet agnostic meaning we're compatible with any wallet provider. Just pass us a wallet object that matches our expected wallet interface based on the chain you're on.

Solana Wallet InterfaceEVM Wallet Interface

// Example of the Solana wallet to pass into wallet property of CoinflowPurchase { publicKey: PublicKey, signMessage: (message: UInt8Array) => Promise<UInt8Array>, sendTransaction: (transaction: Transaction | VersionedTransaction) => Promise<string> }

// Example of the EVM wallet to pass into wallet property of CoinflowPurchase on any supported EVM chain { address: string; sendTransaction: (transaction) => Promise<{hash: string}>; signMessage: (message: string) => Promise<string>; }

Payment Methods Implementation

Approvely supports various payment methods, including credit cards, debit cards, Apple Pay, and Google Pay. These payment methods are eligible for fraud protection coverage, including chargeback protection and 3D Secure (3DS). Approvely recommends first testing payments without fraud protection tools enabled, then upon successful testing, test payments with chargeback protection and 3DS enabled.

For merchants enabling chargeback protection, ensure you:

• Add the chargeback protection script to every page of your site (not just the payment page).
• Pass chargeback protection parameters (e.g., chargebackProtectionData) to Coinflow.

Testing 3DS

When testing 3DS functionality, use 3DS-specific card numbers in the sandbox environment.

FAQ

No Customer Associated with Customer ID

This error is expected for a first-time payer. Approvely creates a customer record after the payer completes their first purchase. The payment method is saved, so the next time the customer returns, their payment method will be automatically available for a faster checkout. A returning customer who has already made a purchase through Approvely will not encounter this error.