16 posts
AI features cost money and touch customer data, so we keep a registry of every one. Here is how a call that is not on the list is refused before anyth...
When an organization sells through our platform, the money should land in its own account. Here is how connected accounts, platform fees, refunds and...
AI work can be inexpensive or surprisingly costly. Here is how we show an estimate first, ask for confirmation and record measured usage so nobody is...
Refunds and disputes are part of selling, not exceptions to it. Here is why we design them before launching any checkout, and what a complete refund f...
The safest way to protect card numbers is to never hold them. Here is how our checkout forms send card details straight to the payment processor inste...
When a request to an outside service ends without a clear answer, retrying can buy the same thing twice. Here is how we lock uncertain outcomes until...
When a payment route is unavailable, it is tempting to quietly try another one. Here is why our payment code stops and says so instead, and what that...
Some features cost us money every time they run. Here is how a prepaid wallet, a debit-first rule and automatic refunds keep usage billing fair and pr...
Networks retry, people double-click and confirmations arrive twice. Here is how idempotency keeps every payment, credit and renewal from happening mor...
A customer returning from checkout is not proof of payment. Here is why paid access, renewals and wallet credits only change after a signed confirmati...
Testing payments is essential, and mixing test transactions with real ones is dangerous. Here is how we keep test and live money clearly separated.
Plans include limits on things like websites, storage and categories. Here is how we enforce them clearly, with notices instead of silent failures and...