Verified BursaPay gateway workflow: Explains the repeat-charge endpoint that uses a customer's authorization code.
1. Overview & Purpose
The gateway guide documents POST /api/v1/payments/charge/ for charging an existing authorization without redirecting the customer through checkout again.
2. Requirements & Setup
The developer must have a valid authorization code and the customer's email.
3. Step-by-Step Workflow
- Store the authorization reference securely according to your application's credential policy.
- Build the charge request with email and amount.
- Include an idempotency key for safe retries.
- Verify the resulting payment.
4. Rules & Troubleshooting
Repeat charges are sensitive because they can move real money in Live Mode.
5. Verification & Next Steps
Use this capability only where the customer authorization and your application policy permit it.