Skip to main content
Waffo Point Topup is Waffo’s point-card top-up API and white-label point-card top-up solution. As a supplier, you connect your point-code inventory or top-up capability, and Waffo Point Topup runs the end-user-facing side on your behalf: a multi-lingual storefront on a dedicated subdomain, global payment methods, merchant-of-record for the sale, and regular settlement. These pages cover the technical integration. For the product introduction, see Point Topup.

​
Terminology

​
Three integration modes

Decision chart for choosing a Waffo Point Topup integration mode based on the supplier's system setup

Online demo site

To see how the three modes work in practice, walk through the end-to-end flows on the demo site.

​
Mode comparison

​
Who provides which endpoint

Waffo provides only two endpoints and one webhook. They live in the Point Topup group of the API Reference. Everything on the supplier side is an optional integration: the specifications in this documentation are samples. If you already have equivalent endpoints, hand your own API documentation to Waffo Point Topup and Waffo adapts to your existing interface.
The minimal Mode C integration is the GET /redirect signed redirect plus the fulfillment result webhook, with no fulfillment endpoint of your own. In that case the webhook only reports PAY_SUCCESS and PAYMENT_FAILED, and you run your own delivery process after receiving PAY_SUCCESS.

​
Preparation per mode

Materials required from the supplier:Integration steps:
1

Provide point code data

Supplier provides point code data offline as Excel/CSV.
2

Import inventory

Waffo Point Topup imports the point codes into the inventory system.
3

Receive the purchase link

Waffo Point Topup provides the purchase link to the supplier.
4

Embed the link

Supplier embeds the purchase link on its own website.
5

Delivery

After a user purchases, Waffo Point Topup sends the point code to the user’s email.
6

Settlement

Waffo Point Topup provides periodic settlement reports.
See Mode A: offline point code import.
Materials required from the supplier:Integration steps:
1

Exchange RSA public keys

Supplier and Waffo Point Topup exchange RSA public keys.
2

Provide API materials

Supplier provides the API key and API documentation.
3

Joint testing

Test the point code retrieval API together.
4

Receive the purchase link

Waffo Point Topup provides the purchase link as a static link.
5

Embed the link

Supplier embeds the link on its own website.
6

Go live

Launch in production.
See Mode B: point code retrieval API.
Materials required from the supplier:Integration steps:
1

Exchange RSA public keys

Supplier and Waffo Point Topup exchange RSA public keys.
2

Provide keys and materials

Supplier provides SECRET_KEY, the API key, and API documentation.
3

Implement URL signing

Supplier implements the URL signature logic on the backend.
4

Joint testing

Test URL signature verification, the direct fulfillment API, the inquiry API (optional), and the fulfillment event webhook (optional).
5

Embed signed redirect links

Supplier integrates the signed redirect links on its website.
6

Go live

Launch in production.
See Mode C: direct fulfillment API.

​
Next steps

Mode A: offline point code import

Point code CSV format, purchase link embedding, and settlement reports.

Mode B: point code retrieval API

Request and response fields plus the idempotency requirement for real-time retrieval.

Mode C: direct fulfillment API

Signed URL redirect, direct fulfillment, and fulfillment inquiry.

API common specifications

Message structure, RSA signing and verification, error codes, and key generation.