Concepts
Integration Patterns
Idempotency
All payment operations support idempotency to prevent duplicate transactions:
- Use unique
idempotencyKeyfor each payment intent - Retry safe operations without risk of duplication
- Consistent responses for repeated requests
Webhooks
Real-time notifications for payment status changes:
- Payment Status Updates: Notifications for state transitions
- Compliance Results: Screening and review outcomes
- Balance Changes: Wallet balance updates
- System Events: Maintenance and operational notifications
Error Handling
Comprehensive error handling with detailed error codes:
- Validation Errors: Invalid request parameters
- Business Logic Errors: Insufficient balance, compliance blocks
- System Errors: Temporary failures, network issues
- Retry Strategies: Guidance for handling different error types
Last modified on