After complete KYB submission and verification.
Find answers to common setup, operations, and payment questions.
From onboarding to settlement and dispute workflows, this guide helps your team run day-to-day payment operations smoothly.
Fast SLAs
Practical Checklists
Risk Ready
After complete KYB submission and verification.
Based on market, acquirer, and payment method.
First response for critical production incidents.
Typical evidence submission window.
Activation usually takes 2-5 business days after complete KYB submission.
Required basics: commercial registration, tax document, ownership details, and bank proof.
Production activation requires successful test transaction and callback verification.
Default settlement cycle: T+2 to T+5 depending on payment method and market.
Daily reconciliation reports include accepted, refunded, reversed, and pending transactions.
Cutoff times differ by corridor; check your merchant dashboard calendar.
Typical evidence window is 5-10 calendar days from dispute notification.
Recommended evidence: invoice, delivery proof, customer communication, and refund policy snapshot.
Track dispute reason codes to reduce recurring preventable losses.
Use test credentials in sandbox before production key issuance and webhook validation.
Track callback signatures and idempotency keys to avoid duplicate processing.
Retry webhooks with exponential backoff and log each retry status.
Enable velocity controls, country rules, and suspicious IP checks for high-risk segments.
Use role-based access and rotate credentials every 90 days for operational security.
Review failed-auth and privilege-change events weekly.
P1 incidents: first response in under 30 minutes, continuous updates until mitigation.
P2 incidents: first response in under 2 hours during support coverage windows.
Include merchant ID, transaction ID, timestamp, and environment in every ticket.
1) Complete KYB, 2) configure callback URL, 3) test payment/refund flow, 4) verify settlement report format, 5) define dispute owner, 6) move to production.
Most requests are about failed callback retries, payout status mismatches, and chargeback evidence formatting. Include transaction IDs in every ticket to speed resolution.
After KYB approval, successful callback validation, and at least one end-to-end test payment and refund flow.
Settlement is not blocked by callback failure, but your internal order status may mismatch. Always queue callback retries and reconciliation checks.
Yes, accelerated settlement terms may be available based on volume, risk profile, and market availability under your commercial agreement.
Large volume spikes, unusual corridor behavior, sanctions alerts, ownership changes, or incomplete periodic KYB refresh data.