Applicable scenarios
- Server-to-server payment processing
- You already have your own hosted checkout page or payment form
- Custom integration requiring maximum flexibility
Integration roadmap
1
Choose the product
Choose one-time payment for single-charge orders, or subscription payment for recurring billing.
2
Integrate required APIs
One-time payment requires order create, order inquiry, and payment notification. Subscription requires subscription create, subscription inquiry, subscription status notification, and subscription payment notification.
3
Add conditional APIs as needed
Add cancel, refund, refund inquiry, refund notification, subscription manage, or subscription change only when your business flow needs them.
4
Use API Reference for field details
Request fields, response fields, enums, and signing rules are maintained in API Reference. Do not copy field definitions from offline PDFs.
5
Test in sandbox
Use Sandbox and testing, including Apple Pay and Google Pay checks if needed.
6
Submit acceptance materials
Download the one-time payment acceptance template or subscription acceptance template, fill in the executed cases, and submit the result to the Waffo technical support group.
Base URL
Request format
- Content-Type:
application/json(UTF-8 encoding) - All requests use HTTP POST
- Request headers must include
X-API-KEYandX-SIGNATURE subscriptionManagementUrlis required for every/api/v1/subscription/createrequest
Response format
codeis"0"indicates success- On failure,
codeis an error code (for example"A0003"), anddatais empty - Response header
X-SIGNATUREcontains the Waffo signature and must be verified