This is the account the demo runs on, so the balance and the state below are its own. A customer's card spends that customer's balance, not this one.
Reading the account.
Each customer holds their own card, funded from their own balance.
These customers are made up for the walkthrough. What decides the answer is where each one's own account stands.
One request does two different jobs. The answer tells us which one happened.
This shows what an approved account gets back. The same request also goes to Whop for real, and its answer is underneath.
A card, the cap we set, and the number behind a button.
The number is never saved anywhere. It shows once, then it is gone after thirty seconds.
Freezing is reversible and it is the right answer to anything that looks wrong. Cancelling is not.
Every purchase arrives with the shop name, the amount, and why it failed if it did.
| Shop | Amount | Status |
|---|---|---|
| AdobeSoftware | $89.99 | declinedcard spending limit exceeded |
| UberTransport | $8.40 | completed |
| AnthropicSoftware | $120.00 | completed |
| VercelSoftware | $20.00 | completed |
| FigmaSoftware | $29.00 | completed |
Whop publishes a webhook every time a card is used, so a real integration reads this as it happens instead of checking on a timer. The last purchase here went over the monthly cap, which is why it did not go through.
Everything the page does behind the scenes shows up here.