> ## Documentation Index
> Fetch the complete documentation index at: https://docs.juicyway.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Capture

> Payment capture is the binding stage in the transaction lifecycle where funds are transferred from the customer's account to your merchant account. This process occurs after successful authorization and represents the final step in completing a payment.

## Overview

<Note>
  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
</Note>

## Supported Payment Methods

<CardGroup cols={2}>
  <Card title="Card Payments" icon="credit-card">
    **Features**

    * Direct capture after authorization

    * 3DS/OTP support where required

    * Partial captures supported

    * Real-time status updates
  </Card>

  <Card title="Bank Transfers" icon="building-columns">
    **Features**

    * Virtual account generation

    * Multiple bank support

    * Automated reconciliation

    * Real-time notifications
  </Card>

  <Card title="Stablecoins" icon="coins">
    **Features**

    * Multi-chain support (ETH, TRX)

    * USDT/USDC acceptance

    * Automated rate conversion

    * Cross-border capability
  </Card>

  <Card title="Binance Pay" icon="wallet">
    **Features**

    * Direct wallet integration

    * Instant settlement

    * Multiple currencies
  </Card>
</CardGroup>

## Processing Times

<AccordionGroup>
  <Accordion title="Card Payments">
    * Standard capture: Near instant

    * 3DS Authentication: 1 - 5 minutes

    * Refunds: 5 - 7 business days
  </Accordion>

  <Accordion title="Bank Transfers">
    * NGN transfers: 1.5 - 10 minutes

    * USD/International: 1 - 3 business days

    * CAD (Interac): 5 - 15 minutes
  </Accordion>

  <Accordion title="Stablecoins">
    * TRX Network: 1-3 minutes

    * ETH Network: 5-30 minutes

    * MATIC Network: 1-5 minutes
  </Accordion>

  <Accordion title="Binance Pay">
    * Standard capture: Near instant

    * Confirmation time: 1-2 minutes
  </Accordion>
</AccordionGroup>

## Capture Flow

The general payment capture process follows these steps:

<Steps>
  <Step title="Verify Session">
    Check that the payment session is valid and in an authorized state
  </Step>

  <Step title="Handle Authentication">
    Complete any required authentication steps:

    * 3D Secure for cards

    * OTP validation

    * PIN verification
  </Step>

  <Step title="Execute Capture">
    Make the API call to capture the payment with:

    * Payment session ID

    * Capture amount (for partial captures)

    * Any method-specific parameters
  </Step>

  <Step title="Process Response">
    Handle the capture response:

    * Success: Update your systems

    * Pending: Wait for webhook

    * Failed: Handle error appropriately
  </Step>

  <Step title="Monitor Status">
    Track the payment status via:

    * Webhook notifications (recommended)

    * Status check endpoints
  </Step>
</Steps>

## Method-Specific Guides

For detailed implementation instructions, see the following guides:

* [Card Payments](/payments/capture-payment/cards)

* [Bank Transfers](/payments/capture-payment/bank-transfer)

* [Stablecoins](/payments/capture-payment/stablecoins-payment)

* [Binance Pay](/payments/capture-payment/binance-pay)

* [Interac e-Transfer](/payments/capture-payment/interac)

## Best Practices

<AccordionGroup>
  <Accordion title="Error Handling">
    * Implement exponential backoff for retries

    * Handle timeouts gracefully

    * Log all capture attempts

    * Monitor failed captures

    * Set appropriate timeout limits
  </Accordion>

  <Accordion title="Security">
    * Validate all capture requests

    * Use HTTPS for API calls

    * Follow PCI compliance for card data

    * Implement proper access controls

    * Rotate API keys regularly
  </Accordion>

  <Accordion title="Monitoring">
    * Track capture success rates

    * Monitor processing times

    * Set up alerts for failures

    * Review capture logs regularly
  </Accordion>

  <Accordion title="Reconciliation">
    * Record all capture attempts

    * Match captures to authorizations

    * Reconcile daily transactions

    * Track partial captures

    * Monitor settlement status
  </Accordion>
</AccordionGroup>

## Testing

<Warning>
  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
</Warning>

## Rate Limits

<Note>
  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
</Note>

<Card title="Need Help?">
  For additional support:

  * Check our [API Reference](/api-reference/overview)

  * Review the [Error Handling Guide](/errors)

  * Contact [support@juicyway.com](mailto:support@juicyway.com)
</Card>