Funding API
Funding sessions abstract card, bank transfer, virtual account, open banking, mobile money, and other provider-specific steps behind an EgaCard session record.
Safety Rules
- Frontend success screens are never treated as final.
- Funding is only matched after webhook verification or provider verification API success.
- Every successful funding produces a financial operation, receipt, notification, and reconciliation status.
Endpoints
| Endpoint | Method | Auth | Headers | Notes |
|---|---|---|---|---|
Create funding session/payment/api/v1/funding/sessions/Start an EgaCard-branded funding flow using the best routed partner. |
POST | User JWT Authenticated user |
Authorization: Bearer <user-jwt>Content-Type: application/json |
Idempotency: Internal session reference plus partner callback verification Webhooks: wallet.credited, payment.successful Sandbox: Supported with sandbox keys and adapters. Production: Available subject to verification, country activation, and provider support. Rate limits: Standard authenticated rate limits |
Verify funding session/payment/api/v1/funding/sessions/{reference}/verify/Confirm provider success and credit the destination wallet. |
POST | User JWT or trusted callback actor Authenticated user or trusted internal callback |
Authorization: Bearer <user-jwt>Content-Type: application/json |
Sandbox: Supported with sandbox keys and adapters. Production: Available subject to verification, country activation, and provider support. Rate limits: Standard authenticated rate limits |
Record incoming issued-account funding/accounting/api/v1/issued-accounts/{reference}/funding/Staff-side endpoint that credits a wallet when a provider confirms incoming funds on an issued account. |
POST | Staff session Staff or automated internal callback |
Session auth |
Sandbox: Supported with sandbox keys and adapters. Production: Available subject to verification, country activation, and provider support. Rate limits: Standard authenticated rate limits |