Reducing Chargeback Risk with Client-Confirmed Billing
How client_confirm capture mode protects your billing
What It Is
Client-confirmed billing uses the `client_confirm` capture mode to send an invoice with a Pay Now button before charging the customer. The client explicitly approves the charge by clicking Pay Now. This creates a documented evidence trail: the invoice sent date, the client's payment timestamp, and the client's IP address — all recorded in `rev_meta`.
Why It Matters
Chargebacks cost more than just the refunded amount. Each one carries a $15–25 dispute fee plus operational time to respond. Variable amounts, deliverable-based billing, and infrequent charges are high-risk categories for `off_session` charges because the customer may not recognize or remember the transaction.
`client_confirm` eliminates "I didn't authorize this" disputes entirely. The customer clicked Pay Now — and you have the timestamp and IP to prove it.
How It Works
The evidence chain has three steps:
Step 1 — Invoice sent. Edge generates an invoice with the description and amount. The sent timestamp is recorded.
Step 2 — Client clicks Pay Now. The client reviews the invoice and clicks Pay Now. Edge logs the payment timestamp and the client's IP address in `rev_meta`.
Step 3 — Chargeback defense. If a chargeback is filed, your evidence includes: the invoice email with send date, the payment confirmation with IP and timestamp, and the matching bank descriptor.
Edge displays an advisory recommending `client_confirm` for `event` and `variable` trigger modes where chargeback risk is higher.
When to Use Each Capture Mode
| Scenario | Capture Mode | Reason |
|---|---|---|
| Wallet top-up | `off_session` | Customer enrolled and expects recurring charges at a known amount. |
| SaaS metered usage | `off_session` | Customer agreed to usage-based billing at signup. Charges are frequent and predictable. |
| Fixed monthly retainer | `off_session` | Same amount every cycle. Customer expects it. |
| Project milestone | `client_confirm` | Variable amount tied to a deliverable. Customer should approve before payment. |
| Variable project billing | `client_confirm` | Amount changes each time. Explicit approval prevents disputes. |
| Infrequent charges | `client_confirm` | Customer may not remember enrolling. Pay Now reminds them and creates evidence. |
Examples
Agency bills $4,500 milestone with client_confirm
An agency fires a `client_confirm` trigger for a $4,500 project milestone. The client clicks **Pay Now** on March 16 from IP `203.0.113.42`. Two months later, a chargeback is filed. The agency submits the invoice email, the Pay Now click with IP and timestamp, and the matching bank descriptor. The chargeback is reversed in the agency's favor.
SaaS uses off_session for wallet top-ups
A SaaS platform charges $50 wallet top-ups via `off_session`. This is appropriate because the customer enrolled in auto-top-up, charges are small and frequent, and there is a history of successful charges establishing the pattern.
