Standard payments are typically “Immediate Sale,” meaning funds are debited simultaneously as the user pays. Auth & Capture splits the payment process into two distinct steps: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.
Core value
Use cases
- AI & usage-based services
- E-commerce: shipment model
- Travel & rentals: deposit model
Ideal for scenarios with high costs and variable fees, such as AI image generation, LLM inference, and cloud compute rental.
| Step | Timing | What happens |
|---|---|---|
| Auth | Before task starts | User submits a complex generation task. The system estimates a maximum fee of $10 and freezes that amount, ensuring the user’s card has sufficient funds to cover the compute cost. |
| Capture | After task ends | The task actually consumed 5,000 tokens valued at 4.50 and automatically releases the remaining $5.50 credit limit. |
Key capabilities & operations
Partial capture
Supports capturing an amount less than the original frozen amount for a pre-authorized order.Scenario: AI task estimated at 4.50.Operation: Initiate a Capture request for 4.50 and automatically releases the remaining $5.50 limit.
Void authorization
You can cancel the transaction at any time before initiating capture.Scenario: AI task failed due to system overload; no actual cost incurred.Operation: Call the Void API.Feature: Zero cost (no processing fees), instant release (user limit restored within minutes) — far superior to refunds, which typically take 3–7 days.
Integration
API integration
Set the parametercapture_method: manual when creating a payment order to enable pre-authorization mode. The default is automatic for immediate sale.
Webhook notifications
The system sends notifications at the following nodes to help you sync business status:| Event | Description |
|---|---|
payment_intent.authorized | Credit limit frozen successfully. You can start the AI task or ship goods. |
payment_intent.captured | Funds debited successfully. Funds are ready for settlement. |
payment_intent.canceled | Pre-authorization voided or expired. |
Frequently asked questions
How long is the pre-authorization valid?
How long is the pre-authorization valid?
Why don't I see the pre-authorized money in my account?
Why don't I see the pre-authorized money in my account?
Do I need to refund if the AI task fails?
Do I need to refund if the AI task fails?
No “Refund” is needed because the money hasn’t actually been taken. You simply need to call the Void interface or do nothing (wait for auto-expiration), and the user’s limit will be restored. This is simpler than the refund process and avoids user confusion over “Charged then Refunded.”
Can I perform multiple captures on a single authorization?
Can I perform multiple captures on a single authorization?
Need help? Contact support