Skip to main content

​
Overview

Before attempting to capture a payment:
  • Ensure you have a valid payment session ID
  • Verify any required authorizations are complete
  • Check that the payment hasn’t expired

​
Supported Payment Methods

Card Payments

Features
  • Direct capture after authorization
  • 3DS/OTP support where required
  • Partial captures supported
  • Real-time status updates

Bank Transfers

Features
  • Virtual account generation
  • Multiple bank support
  • Automated reconciliation
  • Real-time notifications

Stablecoins

Features
  • Multi-chain support (ETH, TRX)
  • USDT/USDC acceptance
  • Automated rate conversion
  • Cross-border capability

Binance Pay

Features
  • Direct wallet integration
  • Instant settlement
  • Multiple currencies

​
Processing Times

  • Standard capture: Near instant
  • 3DS Authentication: 1 - 5 minutes
  • Refunds: 5 - 7 business days
  • NGN transfers: 1.5 - 10 minutes
  • USD/International: 1 - 3 business days
  • CAD (Interac): 5 - 15 minutes
  • TRX Network: 1-3 minutes
  • ETH Network: 5-30 minutes
  • MATIC Network: 1-5 minutes
  • Standard capture: Near instant
  • Confirmation time: 1-2 minutes

​
Capture Flow

The general payment capture process follows these steps:
1

Verify Session

Check that the payment session is valid and in an authorized state
2

Handle Authentication

Complete any required authentication steps:
  • 3D Secure for cards
  • OTP validation
  • PIN verification
3

Execute Capture

Make the API call to capture the payment with:
  • Payment session ID
  • Capture amount (for partial captures)
  • Any method-specific parameters
4

Process Response

Handle the capture response:
  • Success: Update your systems
  • Pending: Wait for webhook
  • Failed: Handle error appropriately
5

Monitor Status

Track the payment status via:
  • Webhook notifications (recommended)
  • Status check endpoints

​
Method-Specific Guides

For detailed implementation instructions, see the following guides:

​
Best Practices

  • Implement exponential backoff for retries
  • Handle timeouts gracefully
  • Log all capture attempts
  • Monitor failed captures
  • Set appropriate timeout limits
  • Validate all capture requests
  • Use HTTPS for API calls
  • Follow PCI compliance for card data
  • Implement proper access controls
  • Rotate API keys regularly
  • Track capture success rates
  • Monitor processing times
  • Set up alerts for failures
  • Review capture logs regularly
  • Record all capture attempts
  • Match captures to authorizations
  • Reconcile daily transactions
  • Track partial captures
  • Monitor settlement status

​
Testing

Always test capture flows in our sandbox environment first:
  • Use test cards for card payments
  • Test different authentication scenarios
  • Verify webhook handling
  • Check error responses

​
Rate Limits

Capture requests are subject to rate limiting:
  • 100 requests per minute per API key
  • Burst limit: 10 requests per second
  • Monitor rate limit headers in responses

Need Help?

For additional support:
⌘I