Skip to main content

Documentation Index

Fetch the complete documentation index at: https://waffo.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Providing clear and stable payment capabilities for individual transactions. Through a unified API interface, we support a wide range of global payment methods, helping merchants complete every transaction efficiently.

What is One-time Payment?

One-time Payment refers to a payment model where a fee is charged for a single, standalone transaction. In this model, every payment is independent, involving no recurring charges or automatic renewals. Due to its clear structure and direct process, it is the most fundamental and common form of payment, applicable to a wide range of business scenarios.

Core capabilities


Supported payment methods

With Waffo, integrate once to support multiple mainstream payment methods—no need to develop separately for each one. View full list of supported payment methods →

Integration mode

Waffo offers three flexible integration modes to meet diverse business scenarios and technical requirements. The differences between these modes are as follows:

Security & compliance

Waffo follows the strictest global financial data security standards to ensure the safety of every transaction.
Waffo protects payment data with tokenization, encrypted transmission, and strict access controls designed for PCI DSS-aligned payment flows.
Contact support for security and compliance details →

Frequently asked questions

Does One-time Payment support refunds?

Yes (subject to the specific payment method’s capabilities). Most mainstream payment methods support refunds. However, whether full or partial refunds are supported strictly depends on the rules and capabilities of the underlying payment method.
All transaction data is synced in real-time to the Waffo Dashboard. It supports filtering by time, amount, and status, as well as exporting reports in CSV format.
Waffo returns specific failure reason codes (e.g., “Insufficient Funds,” “Declined by Issuer”). We recommend that merchants prompt users on the front end to switch payment methods and retry.

Need help? Contact support