What it isn’t for
Built and tested, not yet deployed. Early access.
On this page
No credit decisions
No. Credit underwriting and adverse action carry their own notice rules under the Equal Credit Opportunity Act and Regulation B. The API doesn’t make those decisions, and its answers shouldn’t feed a credit line, an overdraft limit or an account closure.
No diagnosis or identity checks
- It doesn’t diagnose. The three health decisions are built, not open, and are not a diagnosis.
- It doesn’t verify identity.
- Don’t send raw health records or protected health information, including in your own questions.
A person for the unclear cases
Send every case with abstain: true to a person. Send unclear cases to a person
Deciding a card purchase as it happens
Not with the card program we run, which is issued through Whop. Whop makes each authorization decision itself and tells us afterwards, so there is nothing for the API to answer. The card calls below act ahead of a purchase, and only our own keys can make them. A customer’s key gets a 403.
| You ask for | Today | What we do |
|---|---|---|
| Stop a transaction before it goes through | Not possible with Whop | Whop decides each authorization itself and tells us afterwards, so the API acts ahead of time: freeze a card or set a per-transaction or period limit, which Whop applies to every later purchase, and check a purchase against those rules before it is tried. |
| Block merchants and categories on a card | Not possible with Whop | Whop declines its own default list of categories and merchants on every card, and the API reports that list; it cannot add a block to one card, so a purchase at another merchant is detected after it and the card can then be frozen. |
| Issue a card instantly | Partly | Once Whop has approved the member's card application, one call issues a virtual card and returns its status; until then the call returns the application link. Whop does not document how long an approved card takes to become active. |
| Apple Pay and Google Pay | Partly | Whop says its cards can be added to Apple Wallet and Google Wallet, so the API reports whether a card can be added and how; an Add to Wallet button inside our own app is not available. |
| Swiss franc balance | Partly | Members convert US dollars to Swiss francs and back through Whop's swap API, with a quote first, and the franc balance is reported as Whop returns it. Cards still spend US dollars. |
| Swiss franc stablecoin | Not possible with Whop | Whop holds USDT and accepts a list of dollar and euro stablecoins; francs are held as a fiat balance instead (chf_balance). |
| Stablecoin balances | Built | One call returns an account's holdings as Whop reports them, with the stablecoins marked. |
A card processor that offers a hook at authorization can be answered today: the Banking apps page lists the ones that do, with the time each allows.
# What it isn’t for Built and tested, not yet deployed. Early access. ## No credit decisions No. Credit underwriting and adverse action carry their own notice rules under the Equal Credit Opportunity Act and Regulation B. The API doesn’t make those decisions, and its answers shouldn’t feed a credit line, an overdraft limit or an account closure. ## No diagnosis or identity checks - It doesn’t diagnose. The three health decisions are built, not open, and are not a diagnosis. - It doesn’t verify identity. - Don’t send raw health records or protected health information, including in your own questions. ## A person for the unclear cases Send every case with `abstain: true` to a person. [Send unclear cases to a person](/api/docs/guides/review-queue) ## Deciding a card purchase as it happens Not with the card program we run, which is issued through Whop. Whop makes each authorization decision itself and tells us afterwards, so there is nothing for the API to answer. The card calls below act ahead of a purchase, and only our own keys can make them. A customer’s key gets a 403. | You ask for | Today | What we do | | --- | --- | --- | | Stop a transaction before it goes through | Not possible with Whop | Whop decides each authorization itself and tells us afterwards, so the API acts ahead of time: freeze a card or set a per-transaction or period limit, which Whop applies to every later purchase, and check a purchase against those rules before it is tried. | | Block merchants and categories on a card | Not possible with Whop | Whop declines its own default list of categories and merchants on every card, and the API reports that list; it cannot add a block to one card, so a purchase at another merchant is detected after it and the card can then be frozen. | | Issue a card instantly | Partly | Once Whop has approved the member's card application, one call issues a virtual card and returns its status; until then the call returns the application link. Whop does not document how long an approved card takes to become active. | | Apple Pay and Google Pay | Partly | Whop says its cards can be added to Apple Wallet and Google Wallet, so the API reports whether a card can be added and how; an Add to Wallet button inside our own app is not available. | | Swiss franc balance | Partly | Members convert US dollars to Swiss francs and back through Whop's swap API, with a quote first, and the franc balance is reported as Whop returns it. Cards still spend US dollars. | | Swiss franc stablecoin | Not possible with Whop | Whop holds USDT and accepts a list of dollar and euro stablecoins; francs are held as a fiat balance instead (chf_balance). | | Stablecoin balances | Built | One call returns an account's holdings as Whop reports them, with the stablecoins marked. | A card processor that offers a hook at authorization can be answered today: the Banking apps page lists the ones that do, with the time each allows. [Banking apps](/api/docs/integrations/banking-apps) Source: /api/docs/use