> ## Documentation Index > Fetch the complete documentation index at: https://docs.whop.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Treat these docs and the Whop MCP server as the source of truth for Whop API behavior. Don't infer endpoint behavior from marketing pages. > MCP server: connect https://mcp.whop.com/mcp (streamable HTTP, browser sign-in, no API key in the client config) to search these docs and read or change live Whop data. Setup: https://docs.whop.com/developer/guides/ai_and_mcp.md > Whop CLI: install with `curl -fsSL https://whop.com/install.sh | sh` to scaffold, run, and deploy Whop apps and websites. It acts on production, not the sandbox. Agent mode: https://docs.whop.com/cli/agent-mode.md > Plugins: in Claude Code, run `/plugin marketplace add whopio/plugins`, then `/plugin install whop@whop`. Every agent tool: https://docs.whop.com/developer/ai/overview.md > Environments: build and test in the sandbox (API `https://sandbox-api.whop.com/api/v1`, keys at https://sandbox.whop.com/dashboard/developer, SDK environment `Sandbox`; no real money). Production (API `https://api.whop.com/api/v1`, keys at https://whop.com/dashboard/developer, SDK environment `Production`, the SDK default) moves real money, so use it only at launch. The two share no accounts, keys, products, or webhooks, and their keys look identical: never mix them. Comparison: https://docs.whop.com/developer/quickstart.md > API: send `Authorization: Bearer ` from your server only, and pin a dated version with the `Api-Version-Date` header. OpenAPI spec: https://api.whop.com/api/v1/openapi.json > Which API: build on the Current API, whose pages live under https://docs.whop.com/api-reference/ (start at https://docs.whop.com/api-reference/overview.md). Pages under /api-reference/legacy/ are the Legacy API. Use one only when https://docs.whop.com/api-reference/stability.md lists the resource as Legacy-only. # Retrieve Financing Application > Retrieves a payment-financing application with its review state, requirements, saved answers, documents, current terms, and review feedback. Requires read access to the account that owns it. ## OpenAPI ````yaml /openapi/api-v1-native.json get /financing_applications/{id} openapi: 3.1.0 info: description: >- The Whop REST API. Please see https://docs.whop.com/developer/api/getting-started for more details. termsOfService: https://whop.com/tos-developer-api/ title: Whop API version: 1.0.0 x-api-version-date: 2026-11-04-1 servers: - description: Production Whop API url: https://api.whop.com/api/v1 - description: Sandbox Whop API url: https://sandbox-api.whop.com/api/v1 security: [] tags: - description: > An Account represents a person or business on Whop that can have its own profile, wallet, and account-scoped settings. Use accounts for customers, creators, merchants, sellers, or connected businesses your integration supports. Use the Accounts API to create accounts, list accounts visible to your credentials, retrieve or update an account, suspend or delete a subaccount managed by your platform, and retrieve the account associated with the current API key. name: Accounts x-whop-summary: 'A business on Whop: profile, wallet, capabilities, settings.' - description: > A User represents a person on Whop. Users have a public profile and can buy products, join accounts, and access experiences. Use the Users API to search for users, retrieve or update profiles, and check whether a user has access to an account, product, or experience. name: Users x-whop-summary: 'A person on Whop: profile and connected identities.' - description: > A Member is one buyer's relationship with an account: one record per customer, however many memberships they hold. It tracks whether they have joined or left, their access level, and when they last opened the account's content. Use the Members API to list and search an account's members, retrieve a single member, and read a member's activity log. Member rows are created and maintained by the membership lifecycle; to grant or revoke access, work with memberships instead. name: Members x-whop-summary: One buyer's relationship with an account, across all their purchases. - description: > A Team Member is a member of an account's team: the link between a user and an account, carrying the role that controls what they can do. Roles are either system roles (like `admin` or `moderator`) or `custom` roles managed from the dashboard. Use the Team Members API to list an account's team, add a user to the team with a system role, change a member's role, and remove members. Adding a user who has not yet accepted sends an invitation instead. name: Team Members x-whop-summary: An account's team members and the roles that scope their access. - description: > Search finds one account's records in one call: members, memberships, payments, affiliates, reviews, resolution center cases, promo codes and accounts. A pasted identifier finds its records exactly and they come first, ahead of ranked text matches. Use the Search API behind a search box or a command menu over an account's data: find the customer behind an email or a card, open a payment from its ID or invoice number, or jump to a member by name. To filter one resource and page through every match, use that resource's list endpoint instead. name: Search x-whop-summary: >- Find an account's members, payments and other records in one call, by ID, email, card, phone, number, link or text. - description: > An External Account represents an account on another platform linked to a Whop account or user, such as a Facebook page, Instagram account, TikTok account, or Klaviyo account. You connect it through OAuth or an API key, or Whop creates it for you. External account IDs are prefixed `sacc_`. Use the External Accounts API to list connected accounts, [connect a profile through OAuth](/api-reference/external-accounts/connect-an-external-account), [create a Whop-managed Facebook page or TikTok account, or connect a Klaviyo account with its API key](/api-reference/external-accounts/create-an-external-account), and disconnect an external account. name: External Accounts x-whop-summary: Accounts on other platforms linked to an account or user. - description: > Social Accounts is the former public name for External Accounts. Existing integrations can keep calling these deprecated endpoints while they migrate; every response points to the matching External Accounts endpoint. Use the External Accounts API for all new integrations. External account IDs keep their `sacc_` prefix, and the underlying resource is unchanged. name: Social Accounts x-whop-summary: Deprecated compatibility endpoints for external accounts. - description: > A Payment is one charge against a buyer, for one or more variants. Create an on-session payment with a `confirmation_token` for the method the buyer selected, or an off-session payment with an existing member's stored payment method. Use the Payments API to charge buyers, list and retrieve payments, and refund, void, capture, or retry them. Collection runs in the background, so the create response is not the outcome. Poll [Retrieve status](/api-reference/payments/retrieve-payment-status) for how far the payment has gone and, while it is `requires_action`, what the buyer must do next: follow a redirect, complete 3D Secure, display transfer instructions, or link a bank account. Update the payment's `return_url` to change where they land afterwards, up until they come back. name: Payments x-whop-summary: A charge against a buyer, and the step they still owe. - description: > An Invoice is a receipt with an invoice number. Create a draft from variant-backed items, set its recipient and due date, and edit it until it is sent. Its `pay_` ID is also the payment ID when collected. Draft creation does not create access or charge the buyer. The recipient's contact details live on the account's member. Financial fields and caller metadata can only be edited in draft. name: Invoices x-whop-summary: >- A payment request that keeps the same receipt from draft through collection. - description: > A Confirmation Token is a single-use, short-lived reference to a payment method and billing details collected from a buyer. Its response never returns the underlying payment credential. Whop Elements mint the token in your buyer-facing collection flow and hand you its `ctok_` ID to send to the Payments API from your server. Retrieve a token to display its payment method and billing preview or check whether it is still usable. name: Confirmation Tokens x-whop-summary: A short-lived reference to payment details collected from a buyer. - description: > A Payment Quote prices a purchase exactly as a payment for it will be charged: the same line pricing, promo code, and tax, for a buyer located by the address, country, or IP address you send. A quote is priced once, can be consumed by one payment, and expires. Use the Payment Quotes API to show a buyer the total, tax, and currency before they pay, then pass the quote's `id` as `quote_id` when you create the payment to charge exactly that quote. Quote again whenever the cart, promo code, or address changes. name: Payment Quotes x-whop-summary: 'A purchase priced before it is paid: its lines, promo code and tax.' - description: > A Setup Intent saves a buyer's payment method for later without taking money now. Create one from a confirmation token the payment elements collected in setup mode, or from a payment method already on file to re-verify it. It runs the same collection flow a payment does, so the buyer may still owe a step: 3D Secure on a card, a hosted enrollment, or linking a bank account. The create response is the setup intent as created, not its outcome. Hand its `client_secret` to the elements' `handleNextAction`, or poll [Retrieve status](/api-reference/setup-intents/retrieve-setup-status) for how far the setup has gone and what is outstanding. Once it reaches `succeeded`, `payment_method_id` names the saved method and Create Payment charges it. name: Setup Intents x-whop-summary: Saving a buyer's payment method without charging it. - description: > A Refund is one full or partial reversal of a payment, issued with [Refund Payment](/api-reference/payments/refund-payment). It records how much moved, through which provider, and whether it succeeded. Use the Refunds API to list the refunds on a payment or across an account, and to retrieve a single refund. name: Refunds x-whop-summary: Money returned to a buyer from a payment. - description: > A Resolution Center Case is opened by a buyer when something is wrong with a purchase, such as an unwanted renewal, an item that never arrived, or a charge they don't recognize. It is the step before a chargeback: the buyer and merchant work it out directly, and Whop decides the case if they can't. Use the Resolution Center Cases API from either side: as the buyer, open, reply to, appeal, or withdraw a case; as the merchant, accept it (refunding the payment), deny it, or ask the buyer for more information. name: Resolution Center Cases x-whop-summary: File or respond to a case against a payment, as the buyer or the merchant. - description: > A Dispute alert is an early warning from a card issuer that a settled payment is being questioned, ahead of any chargeback. `type` separates fraud reports (`early_fraud_warning`), pre-dispute notices (`dispute_alert`), and Visa RDR cases the network already closed by refunding (`rapid_dispute_resolution`). Use the Dispute alerts API to list alerts for an account, filter them by type or payment, and read `actionable` to see whether refunding can still avoid the chargeback. name: Dispute alerts x-whop-summary: Issuer warnings that arrive before a chargeback does. - description: > A Dispute is a chargeback a customer files against a payment through their bank, or an inquiry that may become one. It carries the disputed payment, a deadline to respond, your evidence, and the outcome once the processor rules. Use the Disputes API to list disputes, edit the evidence packet while a dispute is still contestable, and submit it for review, or accept a chargeback you don't want to contest. name: Disputes x-whop-summary: Chargebacks filed against an account, with evidence and outcomes. - description: > A Payment Rule lets an account act on its own payments before they reach the bank: block them, let them through, send them to review, or ask the buyer for 3D Secure. Each rule matches on a small set of payment attributes, and every condition must hold for it to apply. A rule's definition is fixed once created, so the payments it decided keep naming the rule that decided them. Use [Replace](/api-reference/payment-rules/replace-a-payment-rule) to change one, and [List fields](/api-reference/payment-rules/list-fields) for the attributes, operators and values a condition can use. name: Payment Rules x-whop-summary: Rules an account writes to decide its own payments. - description: > To accept payment-financing methods, an account applies through a financing application: a request to review the account for payment financing, not a loan or business capital. Create an application, save answers to its requirements, then submit it for review. You can manage applications for your own account and its direct subaccounts. name: Financing Applications x-whop-summary: An account's request to accept buy-now-pay-later payment methods. - description: > Deposits describe the ways to add funds to an account or user balance: a hosted deposit page, bank transfer instructions, and crypto wallet addresses. Use the Deposits API to get deposit instructions for an account or user, such as a crypto address to send funds to or bank details for a transfer. name: Deposits x-whop-summary: Add funds to a balance. - description: > A Transfer moves money between Whop balances: from one account or user to another, from an account's wallet to a person or address, or into a claim link anyone with the URL can redeem. Use the Transfers API to send money, find recipients you can pay, list and retrieve transfers when reconciling money movement, and preview or redeem claim links. Subscribe to `transfer.completed` and `transfer.failed` for outcomes instead of polling. Each participating account can subscribe to these events. `transfer.created` is also emitted on success, not when processing starts. A failed transfer can be retried under the same ID and later succeed; retrieve the transfer to reconcile its current status. A successful balance transfer credits the recipient's available balance unless a release date applies. Transfers funded from pending balance retain a release date and credit pending balance; applicable recipient reserves or fraud holds can keep funds unavailable. `succeeded` confirms the transfer completed, not that all funds are withdrawable. name: Transfers x-whop-summary: Move funds between Whop accounts and users. - description: > Payouts represent money sent from an account or user balance to an external destination, such as a bank account, wallet, or other saved payout method. Use the Payouts API to create and track payouts, manage saved payout methods, and show expected arrival details for funds leaving Whop. name: Payouts x-whop-summary: Send money from a balance to a bank or wallet. - description: > A Financial Activity row is a single movement of money in or out of an account's or user's balance: a payment, payout, refund, transfer, on-chain deposit, swap, or card transaction. Each row carries a typed `resource` and `source` so you can present and link the event without extra lookups. Use the Financial Activity API to build a statement or transaction feed for an account or user, and financial reports to summarize balance activity, income, and balances over a date range, then break a report total down into what drove it. name: Ledgers x-whop-docs-title: Financial Activity x-whop-summary: The activity feed behind an account or user's balance. - description: > Cards represent virtual payment cards that spend from an account or user balance. Cards can be assigned to cardholders and configured with spending limits for controlled spending. Use the Cards API to issue cards, list cards for an account or user, retrieve active card details such as the card number and CVC, and list the transactions made with them. name: Cards x-whop-summary: Issue cards that spend from a balance. - description: > A Cashback Rule pays a platform's direct subaccounts back a share of their card spend, funded by the platform. Each rule sets a rate, an eligibility window, and optional merchant filters, and can be limited to one subaccount. Use the Cashback Rules API to create, update, and list the rules your platform funds, then pay out cashback on demand from your available USD balance. name: Cashback Rules x-whop-summary: Configure platform-sponsored card cashback. - description: > A Swap converts value between supported tokens, chains, or wallet destinations, or between fiat currencies at the mid-market rate, for an account or user. A swap quote previews the expected output, fees, and approval requirements before you create the swap. Use the Swaps API to quote a conversion, create the swap, list recent swaps, and retrieve a swap's status until it completes. name: Swaps x-whop-summary: Convert a balance between currencies. - description: > A Trade is one request on an account's or user's Whop-managed wallet. An `order` on a perpetual trades from the trading balance, bridging the USDT0 it needs from the wallet first when the balance is short; an `order` on spot swaps between USDT0 and the asset in the wallet. A `close` closes the whole position in one market; when the account is then flat, a `withdraw` trade sends the trading balance back to the wallet. A `deposit` or `withdraw` moves money between the wallet and the trading balance. Perpetuals trade on Hyperliquid. Use the Trades API to list the markets you can trade, place orders, close positions and move funds, and follow each trade until it finishes. Trades run in the background; an order that bridged money in and does not fill sends that money back to the wallet, and `funds_location` says where the money is. The trading API, including `include_trading` on accounts and users, is in beta. It can change without a new API version date. name: Trades x-whop-summary: >- Place orders, close positions, and move funds for perpetual and spot trading from a Whop-managed wallet. - description: > A Verification represents a legal identity for a person or business. Accounts and users complete verification when Whop needs to confirm who they are before enabling payouts or compliance-sensitive workflows. Use the Verifications API to start or resume a hosted verification session, check review status, and submit requested details or documents. If `requested_information` contains items, submit answers with [Update Verification](/api-reference/verifications/update-verification). name: Verifications x-whop-summary: Legal identity required before payouts and card issuing. - description: > A Product is a digital good or service sold on Whop. Products contain variants for pricing and may contain experiences for content delivery. Use the Products API to search the public marketplace, list an account's products, retrieve a product, and create, update, or delete products. name: Products x-whop-summary: The things you sell. Each owns variants and a store page. - description: > A Variant is one purchasable configuration of a product. It controls price, billing cadence, stock, SKU, attributes, tax behavior, checkout fields, and purchase visibility. Variant IDs remain prefixed `plan_`. Use the Variants API to create variants for products, list existing variants, retrieve or update variant configuration, calculate tax for checkout, and delete variants that should no longer be offered. name: Variants x-whop-summary: Purchasable configurations of a product. - description: > A Promo Code is a discount a buyer enters at checkout, either a percentage or a fixed amount off. It belongs to an account, can be limited to one product, and controls who can redeem it, how many times, until when, and for how many billing periods the discount lasts. Use the Promo Codes API to create codes for an account, list and retrieve them, deactivate a code to pause redemptions or activate it again, and archive codes you no longer offer. name: Promo Codes x-whop-summary: Discounts that creators configure for checkout. - description: > A Checkout Configuration is a reusable checkout link owned by an account. In `payment` mode it sells a specific variant; in `setup` mode it collects and saves payment details without charging. Each configuration can also override which payment methods are accepted and how 3D Secure is enforced for that checkout. Use the Checkout Configurations API to create checkout links for an existing or inline variant, list configurations for an account, retrieve the configuration behind a checkout URL, and delete links that should no longer be used. name: Checkout Configurations x-whop-summary: Turn a variant into a shareable, prefilled checkout link. - description: > A Waitlist Entry is a user's signup for a variant that requires seller approval. Joining doesn't grant a membership or charge a payment method; the seller approves or denies each signup. Use the Waitlist Entries API to join a waitlist, read or cancel your own signups, and approve or deny the signups for accounts you operate. name: Waitlist Entries x-whop-summary: Join waitlists and manage customer signups awaiting approval. - description: > A Membership is a customer's purchase of a variant: the subscription or one-time grant that gives them access to a product. It tracks billing state (`active`, `trialing`, `past_due`, and so on), the current period, pending cancellations, custom metadata, and the software license key when the product includes licensing. Use the Memberships API to list an account's memberships or your own, retrieve one by ID or license key, invite a recipient to join through a free variant, and manage the lifecycle: cancel immediately or at period end, reverse a scheduled cancellation, pause and resume payment collection, extend or reactivate access, apply a promo code or affiliate, change renewal cadence, resync access, generate a transfer link, and update metadata. name: Memberships x-whop-summary: A customer's purchase of a variant, from checkout through cancellation. - description: > A Shipment attaches a carrier tracking number to a payment and follows the package from label creation to delivery, exposing the current delivery status and a customer-facing tracking URL. Use the Shipments API to list an account's shipments, retrieve one by its ID or the payment it fulfills, attach a tracking number to a payment, and update the tracking number on an existing shipment. name: Shipments x-whop-summary: Track the delivery of an order by its carrier tracking number. - description: > A Review is a customer's star rating and optional written feedback on a product, shown on the product's store page. Use the Reviews API to list a product's reviews, filtered by star rating or creation date, and retrieve a review by ID. name: Reviews x-whop-summary: Customer star ratings and written feedback on a product. - description: > A Review Report is a request from an account's admins for Whop staff to review a customer's review. Staff remove the review if it breaks the guidelines. Use the Review Reports API to list the reports filed on an account's reviews, narrowed by review, status, or creation date, and check whether a report is still pending. name: Review reports x-whop-summary: Reports an account's admins filed against customer reviews. - description: > A Product Affiliate represents a user's enrollment in a product's affiliate program. An enrollment can exist before the user makes a referral or earns a reward. Use the Product Affiliates API to list product affiliates for an account, search by affiliate name or username, and narrow the results by product, enrollment status, or signup date. name: Product Affiliates x-whop-summary: >- Users enrolled to promote a product, including affiliates with no referrals. - description: > A Domain is a hostname an account holds on Whop. Its capabilities set what Whop does with it: `registration` buys the domain through Whop, runs its DNS, and renews it every year; `verification` connects a domain registered elsewhere once you publish the DNS records it returns, and expires if ownership is not proven within 48 hours; `website` serves one of the account's apps on it. Use the Domains API to search for a domain to buy, buy or connect one, serve a website on it, and check its DNS, payment, and renewal state. Thirty days before a bought domain expires, Whop opens a renewal charge at `purchase_url` and, while `auto_renew` is on, charges the saved card. An unpaid domain stops serving when it expires but stays renewable at `purchase_url` until the registry's grace period ends, and is then removed. name: Domains x-whop-summary: Custom domains assigned to hosted apps. - description: > An App is software you build on Whop. It can be a hosted web app served at its domains, such as a `whop.site` address or a custom domain, or an API integration installed as an experience, and it belongs to the account that owns its credentials, settings, builds, and runtime logs. Use the Apps API to manage app configuration, deploy an app's working copy and follow the run on the app's `deployment` field, and, for hosted apps, read server runtime logs for console output, uncaught exceptions, and failed requests. Apps are also reusable blueprints. List official blueprints with `app_type=website&verified=true&order=template_usage`, or community blueprints with `app_type=website&verified=false&recommended=true&order=template_usage`. Pass the returned App `id` as `blueprint_id` when creating an Account. name: Apps x-whop-summary: 'Apps you build on Whop: metadata, hosted builds, runtime logs.' - description: > An App Build is a versioned artifact uploaded for an app — a hosted web archive, or an iOS/Android bundle. Builds start as drafts, go through review, and one approved build per platform is served to users as the production build. Use the App Builds API to upload a build for an app, list an app's builds with platform and status filters, retrieve a build, and promote a draft or approved build to production. name: App Builds x-whop-summary: Versioned build artifacts deployed to an app's platforms. - description: > An App Installation represents one install of your app on one account. An account installs an app once, however many experiences it adds, so an installation holds state that belongs to the account rather than to one experience, such as a sync cursor or the ID of the account it's linked to in another system. Use the App Installations API to [list the accounts your app is installed on](/api-reference/app-installations/list-app-installations), [retrieve one](/api-reference/app-installations/retrieve-app-installation), and [update](/api-reference/app-installations/update-app-installation) the `metadata` and `external_id` your app keeps on it. An account can also list the apps installed on it, and a developer every installation of their app. Only the app and its developer see `metadata` and `external_id`, and only the app can change them. name: App Installations x-whop-summary: >- Your app's installations on accounts, and the data it keeps about each one. - description: > An Experiment is a feature flag or A/B test owned by an account. Treatments take stable percentage ranges of traffic and everyone else gets control, so growing an allocation never moves an existing user to another arm. Use the Experiments API to create a draft, configure its weights, targeting, and resource bindings, then activate, pause, or end it, and to evaluate which arm a user, account, or anonymous visitor gets. Managing experiments requires `experiment:read` or `experiment:manage`; evaluation works without authentication. name: Experiments x-whop-summary: Feature flags and A/B experiments for gradual rollout. - description: > An Ad Campaign is the top-level container for paid ads. It sets the objective and budget strategy shared by its [ad groups](/api-reference/ad-groups/ad-group) and ads. Use the Ad Campaigns API to create campaigns, list campaigns for an account, retrieve or update campaign settings, and pause or resume campaign delivery. Ads billing combines eligible spend across the account's campaigns. A failed payment blocks delivery with `delivery_status: payment_failed` while preserving the configured active/paused `status`. Fix the account's payment method and [retry its ads payment](/api-reference/accounts/retry-failed-ads-payments) once for the account. The retry is asynchronous: acceptance does not confirm payment. Successful settlement clears the block; active campaigns can resume if otherwise eligible, while paused campaigns stay paused. See [billing and retries](/developer/ads/overview#paying-for-ads). name: Ad Campaigns x-whop-summary: Objective and budget for a set of ads. - description: > An Ad Group sits inside an [ad campaign](/api-reference/ad-campaigns/ad-campaign) and controls delivery for [ads](/api-reference/ads/ad). It sets the audience, schedule, and budget for its ads. Use the Ad Groups API to create ad groups in campaigns, list or retrieve targeting and delivery settings, update budgets or targeting, delete groups that should stop running, and pause or resume delivery. name: Ad Groups x-whop-summary: Audience, schedule, and budget within a campaign. - description: > An Ad is the individual creative unit delivered by an [ad group](/api-reference/ad-groups/ad-group). It holds the copy, creative assets, and destination URL for one ad. Use the Ads API to list ads for an account, create ads inside ad groups, retrieve or update creative details, delete ads that should stop running, and pause or resume delivery. name: Ads x-whop-summary: 'The creative: copy, assets, and destination URL.' - description: > An Audience is a reusable group of people to include or exclude when targeting ads. Build custom audiences from customer lists or Whop People data, and create lookalikes to reach people similar to an existing audience. Use the Audiences API to create audiences, add people to an uploaded customer list, rename or refilter an audience, and monitor asynchronous processing. Whop People audiences can refresh automatically or keep a snapshot. name: Audiences x-whop-summary: Reusable targeting lists for ad groups. - description: > An Ad Pixel connects a pixel you own on an ad platform to a business whose campaigns you claimed through the advertiser supplier program. Whop sends that pixel the conversions credited to your claimed campaigns for that business, using the access token you provide. Use the Ad Pixels API to add one pixel per business on each ad platform, list or retrieve your pixels, replace an access token the ad platform rejected, and remove a pixel to stop deliveries. name: Ad Pixels x-whop-summary: Your own pixels that receive conversions from campaigns you claimed. - description: > Stats represent aggregated activity for an account over time. They help you understand revenue, transactions, disputes, members, referrals, and advertising performance across reporting periods like days, weeks, or months. Use the Stats API to list the metrics you can chart and retrieve one as a time series over a date range, or list reports and retrieve aggregates that are not bucketed over time, such as platform-wide payment trends. name: Stats x-whop-summary: Aggregated financial, audience, and traffic reporting. - description: > A Person is an identity-linked profile of a visitor or customer of an account, assembled from every [event](/api-reference/events/event) the person generated, such as pixel page views, ad clicks, leads, and payments. Use the People API to list and segment the people of an account by activity, purchases, traffic source, or marketing touch, and to retrieve one person by person ID, user ID, email address, or phone number. name: People x-whop-summary: >- Visitors and customers of an account, with identity, purchase, and traffic profiles. - description: > An Event records conversion or engagement activity for an account, such as page views, purchases, or leads. Each event ties the action to the [person](/api-reference/people/person) who took it, so activity can be attributed to the ads and links that drove it. Use the Events API to send new tracking events, list recent identity-linked events for an account, and inspect the events recorded for a person. The resource also exposes an anonymized read mode — the pulse feed — a platform-wide snapshot of recent purchases that carries nothing identifying. The pulse feed is public; other Events endpoints require authentication and are scoped to an account. Events are only as good as the pixel sending them, so [Validate Pixel](/api-reference/events/validate-pixel) answers whether an account's pixel is working: it reads the events the pixel has sent, and when you pass a `url` whose page hasn't sent any lately, it fetches that page and looks for the pixel in its source. Use it before launching an ad to confirm its destination is tracked, or in a setup flow to tell a merchant whether their install is live. name: Events x-whop-summary: Conversion and engagement events tracked for attribution. - description: > An Export is a CSV of one of an account's dashboard tables, such as members, payments, or disputes. Exports are generated in the background, so a new export starts `pending` and becomes `completed` with a download link. Use the Exports API to start an export, poll it until `download_url` is set, and list an account's past exports. Each table requires its own export scope, and finished files are deleted after 30 days. name: Exports x-whop-summary: Asynchronous CSV dumps of an account's dashboard data. - description: > Economic Intelligence is Whop's recommendation engine for an account. Each recommendation is one action: a title the owner sees, a step-by-step brief Whop AI carries out, and the result it expects. Whop generates them from the account's sales, site, ads, and what its owner has said. Use the Economic Intelligence API to list an account's recommendations, request new ones for a specific goal, and follow each one from `queued` to `ready`, then to `executed` once the owner runs it or `superseded` when a newer one replaces it or you retire it. Read `economic_intelligence_offers` from account preferences and send one of its keys as `economic_intelligence_duration_key` to turn it on. name: Economic Intelligence x-whop-summary: What an account should do next to grow, generated from its own data. - description: > A Livestream represents a live video broadcast in an experience. After a recorded livestream ends, members can watch the replay, and moderators can pin the best recordings to feature them. Use the Livestreams API to [list an experience's livestreams](/api-reference/livestreams/list-livestreams), [retrieve one](/api-reference/livestreams/retrieve-livestream) with its recording, and [pin](/api-reference/livestreams/pin-livestream) or [unpin](/api-reference/livestreams/unpin-livestream) recordings. name: Livestreams x-whop-summary: Live video broadcasts in an experience, and their recordings. - description: > A Notification is a message delivered to a user, such as a new post, a payment, or a mention. Each one comes from an experience the user belongs to or a team they are on, and falls under a topic, like new sales, that users set preferences on. Use the Notifications API to list a user's feed, read and clear unread badges, send notifications from your app to an experience's users or an account's team, and list the topic catalog that notification preferences reference. name: Notifications x-whop-summary: >- The user's notification feed: unread badges, mark-read, app sends, and the topic catalog. - description: > An Email address is a mailbox on one of the account's domains, such as support@example.com. The domain needs the `email` capability in the `ready` state first. A mailbox either belongs to one team member, who alone can read it and send from it, or is shared by the account, where `email:read` and `email:send` decide who can use it. Use the Email addresses API to create, list, reassign and delete mailboxes, read the password mail apps sign in with, and download a configuration profile that adds the mailbox to Mail on Apple devices. Deleting an address keeps its mail, and creating it again in the same account brings the mailbox back. name: Email addresses x-whop-summary: Mailboxes on an account's domains, for sending and receiving email. - description: > Get started at [whop.com/network](https://whop.com/network). A Partner is a user who refers people and businesses to Whop. The partner profile includes enrollment, active direct business referral counts, and default payout terms. Retrieve your profile with `/partners/me`. Use `/partner_referral_requests` to create and manage referral links and their rewards. You can also enroll in the partner program, review referred users and businesses, track earnings, and see the partner leaderboard. name: Partners x-whop-summary: >- Your partner profile, referral links, payout rates, and referred businesses. - description: > A Partner Referral Request is a partner's referral link, or a request to be credited as the referrer of an existing business or user. An attribution request takes effect only when the recipient accepts it. Use the Partner Referral Requests API to create referral links, send attribution requests, list the links and requests you've sent or received, and accept, decline, or cancel a pending request. name: Partner Referral Requests x-whop-summary: Request business or partner attribution and manage approval. - description: > A Bounty is a paid task posted by an account or user. The reward is held in escrow when the bounty publishes, workers submit proof of completed work, and each accepted submission is paid out until every winner slot fills. Use the Bounties API to create and publish a bounty, list an account's bounties for reporting or dashboards, list the bounties a user can work or has participated in, and retrieve a single bounty by ID. name: Bounties x-whop-summary: Paid tasks with reviewed submissions and escrowed rewards. - description: > A Bounty Submission is one worker's attempt on a bounty. It starts as an in-progress attempt, enters the review queue when proof is submitted, and ends approved (paid from the bounty's escrowed pool) or denied. Use the Bounty Submissions API to submit proof of completed work to a bounty, list the submissions you authored, and review the submissions on your bounties — across every bounty or narrowed to one. name: Bounty Submissions x-whop-summary: Work submitted to a bounty, from attempt to payout. - description: > A File is an uploaded document or media object, identified by a `file_` ID. Creating a file returns a presigned destination; upload the bytes there and the file becomes `ready`. Use the Files API to create a file, upload its content directly to storage (in one PUT, or in parts for large files), and retrieve it while polling for readiness. A ready file's ID can be attached wherever Whop accepts files. name: Files x-whop-summary: Upload files and attach them wherever Whop accepts documents. - description: > A Media Asset is an AI-generated image or video created from a prompt and billed from an account balance. When generation finishes, the asset includes a file that can be attached anywhere Whop accepts files. Use the Media API to start a generation job and retrieve the asset while it processes or after it is ready. name: Media x-whop-summary: >- AI-generated assets, billed from a balance, attachable wherever files are accepted. - description: > An API Key is a programmatic credential owned by an account or app. Each key carries its own permissions policy — explicit permission statements or an inherited system role — and can be restricted with an expiration date and an IP allowlist. Use the API Keys API to list an account or app's keys, create a key (the full secret is returned once, on creation), inspect a key's effective grants, update its name or restrictions, rotate its secret, and revoke it. These endpoints require a user session — they cannot be called with an API key. name: API Keys x-whop-summary: Programmatic credentials for an account or app. - description: > A Webhook is an endpoint on your server that Whop sends signed HTTP POST requests to when events happen, such as a payment succeeding or a membership going active. A webhook is attached to an account or an app and subscribes to the events you choose. Use the Webhooks API to create and update endpoints, send a test event, inspect the delivery log, and replay deliveries your server missed. See [Webhooks & Events](/developer/guides/webhooks) for verifying signatures and handling retries. name: Webhooks x-whop-summary: Event notifications pushed to your server as things happen. - description: > A Permission is one action, such as `stats:read`, paired with whether your credential is granted it on a given resource. It answers for whatever you authenticated with, so you can decide what to show or attempt instead of discovering a `403`. Use the Permissions API to check an account, product, experience, or app, narrowing to the actions you care about. It reports only your own access — to manage who else can reach an account, use the Team Members API. name: Permissions x-whop-summary: What your credential is allowed to do on a resource. - description: > An Api Log is a record of a single request made to Whop's API using one of your account's API keys — the programmatic counterpart to the dashboard audit log, which only records actions taken by signed-in team members. Reads and failed requests are logged too. Use the Api Logs API to see what your integrations are doing on Whop: the operation, HTTP method and status, outcome, and timing of each request, newest first. name: Api Logs x-whop-summary: Requests made to Whop's API with your account's API keys. - description: > A feedback submission sends an issue, confusing behavior, documentation gap, or unanswered question to Whop. It is recorded under the authenticated user, account, or app, with an optional account for context, and reviewed by Whop. User, account, and app credentials can all submit. The response is a receipt with an `fbk_` ID: Whop does not reply to submissions, and they cannot be listed or retrieved through the API. name: Feedback x-whop-summary: Issues and unanswered questions sent to Whop for review. paths: /financing_applications/{id}: parameters: - $ref: '#/components/parameters/ApiVersionDate' - description: Financing application ID, prefixed `inrq_`. in: path name: id required: true schema: type: string get: tags: - Financing Applications summary: Retrieve Financing Application description: >- Retrieves a payment-financing application with its review state, requirements, saved answers, documents, current terms, and review feedback. Requires read access to the account that owns it. operationId: retrieveFinancingApplication responses: '200': content: application/json: schema: $ref: '#/components/schemas/FinancingApplication' description: Application returned '401': $ref: '#/components/responses/Unauthorized' description: Authentication required '403': $ref: '#/components/responses/Forbidden' description: Read permission required '404': $ref: '#/components/responses/NotFound' description: Application not found security: - accountApiKeyOrAccountTokenOrOauthTokenAuth: - payout:account:read components: parameters: ApiVersionDate: description: Pins the request to a dated API version. in: header name: Api-Version-Date required: false schema: example: 2026-11-04-1 type: string schemas: FinancingApplication: properties: account_id: description: >- The ID of the merchant account applying for payment financing, starting with biz_. example: biz_xxxxxxxxxxxxxx type: string created_at: description: When the application was created, as an ISO 8601 timestamp. example: '2026-01-01T12:00:00.000Z' type: string feedback: description: >- Public review feedback when more information is requested or the application is denied. Internal notes are never included. example: null type: - string - 'null' id: description: The financing application ID, starting with inrq_. example: inrq_xxxxxxxxxxxxxx type: string requirements: items: $ref: '#/components/schemas/FinancingRequirement' description: >- Merchant requirements and saved answers. Present on individual application responses, omitted from lists. Acceptance is collected separately on submit. type: array status: description: >- The application's review state. Approval does not by itself indicate that financing payment methods are enabled on the account. enum: - requires_collection - awaiting_review - completed - approved - denied example: requires_collection type: string terms: $ref: '#/components/schemas/FinancingTerms' description: >- Current terms to present before submitting. Present on individual application responses. updated_at: description: When the application was last updated, as an ISO 8601 timestamp. example: '2026-01-01T12:00:00.000Z' type: string required: - id - account_id - status - created_at - updated_at type: object FinancingRequirement: properties: accepted_file_formats: items: description: Accepted document formats, such as pdf or jpeg. type: string type: array field: description: >- The information requested, such as business_description or processing_statements. example: business_description type: string file_collection_type: description: >- Whether the requirement accepts no file, one file, or multiple files. enum: - none - single - multi example: none type: string files: items: $ref: '#/components/schemas/File' description: >- Files attached to this requirement, including expiring download URLs. type: array id: description: Requirement ID to use when updating this application's answers. example: inrqi_xxxxxxxxxxxxxx type: string max_file_size: description: Maximum size in bytes for each uploaded document. example: 20971520 type: integer minimum_length: description: Minimum characters per text answer, when specified. example: 100 type: - integer - 'null' money: description: >- Saved maximum product price in its original currency. Null when unanswered or the saved legacy answer is invalid. oneOf: - $ref: '#/components/schemas/Money' - type: 'null' options: items: description: >- Allowed dropdown values. Empty when the answer is not an enumeration. type: string type: array required: description: Whether this requirement must be completed before submission. example: true type: boolean text_collection_type: description: >- Whether the requirement accepts no text, one value, or multiple values. enum: - none - single - multi example: single type: string text_format: description: >- Expected text format. max_product_price uses money instead of values. enum: - plain - url - email - phone - number - checkbox - dropdown example: plain type: string values: items: description: >- Saved text answers. Empty for money requirements; read money instead. example: https://shop.example.com/shop type: string type: array required: - id - field - required - text_collection_type - file_collection_type - text_format - values - money - files - minimum_length - options - accepted_file_formats - max_file_size type: object FinancingTerms: properties: content: description: >- The exact plain-text contract snapshot covered by this version. Present this content, the policies, and the disclosure before collecting acceptance. example: "https://whop.com/splitit-terms/\_\n\nWe are a retailer of goods or services that you are seeking to purchase (“us“, “our”, “we” or “Merchant”). This Retail Installment Contract Terms & Conditions (“Agreement”) is between us and you, the cardholder, who is making the purchase (“Buyer”, “you“, “your”).\n\nThese terms are in addition to our normal terms of business, including our Return Policy. By choosing to make this purchase using installments, you agree to be bound by this agreement. These additional terms for payment by installment apply when you select the option of paying for your purchase by installments, using a payment card issued by a credit card issuer (“Issuer”). In order to process card payments by installment, we are using a third party technology service provided by Splitit USA Inc. (“Splitit” or “Service Provider”), but you have not entered into an agreement with Splitit.\n\nHow it Works. By selecting the “Splitit” payment option at the checkout page, you authorize us to put a hold on your payment card for the Total Sale Price (as defined below under xxxxxxxxxxxxxx), however we will only charge the eligible card provided to us over time in the number of payments and amounts that you selected at checkout (we call these payments “xxxxxxxxxxxx“). The date and amount of each Installment is shown at checkout before you complete your purchase and a complete record is emailed to you immediately after you complete your purchase. We will charge the initial payment to your card when your order is completed (or later, if shipment is later, in accordance with the payment schedule). Each subsequent Installment is charged monthly, on the dates shown in the payment schedule presented to you at checkout, until the entire amount due under this Agreement is paid. As further described under the xxxxxxxxxxxxxx section, your credit card is eligible if there is available credit (or balance, in the case of a debit card) to support an xxxxxxxxxxxxx for the Total Sale Price and you are authorized to use the payment card to make the transaction. If we are not able to renew an authorization for the amount you owe by your next Installment due date we may charge your card for the Total Sale Price, less the amount of any xxxxxxxxxxxx you have already paid.\n\nNeither we nor Splitit impose any interest or additional charges on you for selecting this payment option. However, we are required by law to warn you that you may have to pay other taxes or costs that are not imposed by us (such as internet charges, fees and interest imposed by the Issuer, or charges imposed by customs in your country). IN PARTICULAR, PLEASE NOTE, AS INSTALLMENT PAYMENTS ARE BEING CHARGED TO YOUR CARD, YOU MAY BE CHARGED INTEREST AND FEES OR OTHER CHARGES IMPOSED BY YOUR CARD ISSUER UNDER THEIR AGREEMENT WITH YOU. THIS COULD INCLUDE LATE PAYMENT FEES, OVERDRAFT FEES, PERIODIC INTEREST, OR OVER-THE-LIMIT FEES. YOU ARE SOLELY RESPONSIBLE FOR THESE FEES.\n\nxxxxxxxxxxxxxx. If you provide a credit card to make payments, we may obtain an authorization against your credit card for up to the total amount of your purchase (“Total Sale Price”). An “authorization” means that the available credit on your credit card will be reduced by an amount, up to the Total Sale Price, in order to ensure you have sufficient available credit to make future payments. You will likely not be able to use that amount of your credit line while the authorization remains in place, subject to rules imposed by your Issuer. Even if your Issuer does not restrict the available credit, you must ensure that you have enough available credit to cover the full outstanding amount owed under this Agreement for your purchase at all times.\n\nTo ensure we retain a valid authorization against your credit card, we may need to renew the authorization periodically using the credit card details provided at the time of purchase (or a subsequent credit card you provide). The amount of any new authorization or any reauthorization will equal the current outstanding value of your installment plan. It may take up to 5 days for the amount of the authorization to be reduced after you make a payment. We will notify you by email approximately 24 hours before the authorization is renewed.\n\nIf any authorization we seek to make against your credit card fails, we will contact you by email (using the email address you provided at checkout) to let you know. We may also contact you via SMS to the extent you have authorized us to do so. We will also keep attempting to get approval for the authorization by submitting a request to your payment card periodically for up to 7 days. You can provide us with a different eligible credit card to use for authorizations and xxxxxxxxxxxx via the consumer portal, using the unique link we email to you when you enter into this Agreement (“Portal“). By providing a new credit card, you authorize us to obtain authorizations for the remaining amounts owed under this Agreement, as set forth in this Agreement, and you further authorize us to charge this updated credit card for outstanding xxxxxxxxxxxx owed, when due under this Agreement. You also authorize us to charge or refund your credit card as necessary to correct any errors. If we are not able to renew an authorization for the amount you owe under this Agreement by your next Installment due date, and you do not make an Installment payment by the due date (subject to any applicable grace period) or successfully authorize those amounts on another eligible card, we may charge your credit card for the Total Sale Price, less the amount of any xxxxxxxxxxxx you have already paid.\n\nTHIS AGREEMENT INCLUDES AN ARBITRATION AGREEMENT. IT WILL HAVE A SUBSTANTIAL EFFECT ON YOUR RIGHTS IN THE EVENT OF A DISPUTE UNLESS YOU: (1) OPT OUT WITHIN 30 DAYS OF SIGNING THIS AGREEMENT; OR (2) ARE PROTECTED BY THE MILITARY LENDING ACT. YOU WILL NOT HAVE THE RIGHT TO A JURY TRIAL OR THE RIGHT TO PARTICIPATE IN A CLASS ACTION IN COURT OR IN ARBITRATION.\n\nRight to Stop Payment; Changing your Payment Method: You have a right to stop payment on your selected credit or debit card by writing to our Service Provider by email at support@splitit.com, or by providing a new eligible card in the Portal. You must tell our Service Provider in time for us to receive your request at least 3 business days before your next Installment due date. If you call, we may require you to confirm your request in writing within 14 days after your call. If your credit or debit card is replaced, cancelled, no longer valid, or you wish to use a different card, you must log on to the Portal and provide an eligible card at least 3 business days before your next Installment due date. We may not be able to process your request if we do not receive it in time. If you do not have sufficient available credit or available funds on the new card to process the authorization, we may not accept the card.\n\nIt is your responsibility to ensure that, until the last Installment is paid, the card you present for payment at the time of purchase, or anytime thereafter, remains valid, is not cancelled, and has sufficient available balance or available credit to pay all xxxxxxxxxxxx and to accept authorizations that may be made under this Agreement.\n\nPAYMENT AUTHORIZATION: BY ACCEPTING THIS AGREEMENT, YOU AUTHORIZE US OR OUR SERVICE PROVIDER TO (1) AUTHORIZE YOUR SELECTED CARD FOR UP TO THE TOTAL SALE PRICE AS DESCRIBED ABOVE; (2) CHARGE YOUR SELECTED CARD FOR THE AMOUNT OF YOUR FIRST INSTALLMENT ON OR AFTER THE DATE OF THIS AGREEMENT; (3) CHARGE YOUR SELECTED CARD IN THE AMOUNT OF EACH INSTALLMENT ON EACH INSTALLMENT DUE DATE AS DESCRIBED IN YOUR TRUTH IN LENDING DISCLOSURES AND PAYMENT SCHEDULE; (4) CHARGE YOUR SELECTED CARD FOR THE TOTAL SALE PRICE LESS ANY INSTALLMENTS YOU HAVE ALREADY PAID (A) IN AN EVENT OF DEFAULT (SUBJECT TO ANY NOTICE AND CURE RIGHTS YOU MAY HAVE BY LAW) OR (B) IF YOU CANCEL THIS AGREEMENT AFTER THE TIME PERMITTED BY THIS AGREEMENT; AND (5) CHARGE YOUR SELECTED CARD AS NECESSARY TO CORRECT ANY ERRORS. THIS PAYMENT AUTHORIZATION WILL REMAIN IN FULL FORCE AND EFFECT UNTIL ALL INSTALLMENTS ARE PAID IN FULL OR WE RECEIVE NOTICE THAT YOU REVOKE THIS AUTHORIZATION.\n\nHandling Card Payments and xxxxxxxxxxxxx. We use a third-party technology platform provided by Splitit to keep a record of payments you owe us and we use their platform to process authorizations and payments at the times we have agreed and to send notifications to you. You will see some of the emails say they are “powered by Splitit”. This should help you identify what payments we are contacting you about.\n\nReturns. You may return the goods to us as set forth in our Return Policy.\n\nxxxxxxxxxxxx. You have the right to cancel this Agreement to pay for your purchase using xxxxxxxxxxxx at any time, but once you cancel this Agreement, the Total Sale Price less any amounts already paid will become due in full. To request a cancellation, please contact our Service Provider by email at support@splitit.com.\_\n\nDefault. Subject to applicable law, which may require that we notify and/or give you a right to cure your default, we may declare you in default under this Agreement for any of the following reasons: (1) you fail to pay any Installment by the due date, and after any applicable grace period; (2) you violate any promise you make to us in this Agreement which significantly impairs your ability to pay or our ability to collect the amounts due under this Agreement; (3) you file for protection under the United States Bankruptcy Code, or become subject to a proceeding which seeks relief from debt; (4) you have made a false or misleading statement about an important matter in connection with this Agreement; (5) you revoke your consent to electronic communications; or (6) you die or become legally incompetent.\n\nxxxxxxxxxxxx of Default. If you are in default of this Agreement, we can require you to pay the remaining amount you owe us under this Agreement immediately, subject to any right you may have to notice of default and to cure such default. We may seek payment of this amount by charging your credit or debit card pursuant to any authorization you provided us under this Agreement. If we refer this Agreement to an attorney who is not our salaried employee for collection, we may require you to pay our reasonable attorneys’ fees and expenses, to the extent permitted by applicable law.\n\nAssignment. You are hereby notified and agree that we may transfer, sell, or assign this Agreement, the xxxxxxxxxxxx, or any associated rights, to a third party, including Splitit or one of its affiliates, without any further notification to you. If we do so, this Agreement will remain in effect and will be binding on and will inure to the benefit of our assign(s). You may not transfer your rights under this Agreement and any attempt to do so will be void.\n\nGoverning law; xxxxxxxxxxxx. This Agreement (and our dealing prior to this Agreement being made) shall be governed by federal law, and to the extent not pre-empted, the laws of the state in which you purchased the goods and services; provided that you are entitled to the benefit of any mandatory consumer protection rules of the country of your primary residence. If any provision of this Agreement or portion thereof is held to be unenforceable, this determination will not affect the remainder of this Agreement.\n\nIndemnity and Limitation of Liability. You agree to indemnify, defend, and hold us, our service providers, and our respective agents, officers, directors, employees and assigns (collectively, the “Indemnified Parties”) harmless from and against any liability, including reasonable attorneys’ fees, related to this Agreement. THE INDEMNIFIED PARTIES WILL NOT BE LIABLE FOR INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES REGARDLESS OF THE FORM OF ACTION AND EVEN IF WE HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IF WE FAIL TO STOP PAYMENT ON AN ITEM, OR PAY AN ITEM BEARING AN UNAUTHORIZED SIGNATURE, FORGED SIGNATURE, OR FORGED ENDORSEMENT OR ALTERATION, OUR LIABILITY, IF ANY, WILL BE LIMITED TO THE FACE AMOUNT OF THE ITEM. The foregoing limitation of liability will not apply where expressly prohibited by the laws governing this Agreement. This Limitation of Liability section will survive termination of this Agreement.\n\nArbitration Agreement. We are always interested in resolving disputes, claims, or controversies (“Claim”) amicably and efficiently, and most customer concerns can be resolved quickly and to the customer’s satisfaction by contacting us by email through our Service Provider at support@splitit.com or by mail at Splitit USA, Inc., 211 Perimeter Center Pkwy NW, Suite 240, Atlanta, GA 30346. If such efforts prove unsuccessful, you and we agree that all disputes shall be resolved by binding arbitration on an individual basis. A party who intends to seek arbitration must first send to the other, by certified mail, a written Notice of Dispute (“Notice”). The Notice must (a) describe the nature and basis of the Claim and (b) set forth the specific relief sought. If you do not resolve the Claim with us or the Indemnified Party within 60 calendar days after the Notice is received, you, we or the Indemnified Party, as applicable, may commence an arbitration proceeding, as set forth in this section. Arbitration will be conducted by a neutral arbitrator in accordance with the AAA rules and procedures, including the AAA’s Consumer Arbitration Rules (collectively, the “AAA Rules”), as modified by this Arbitration Agreement. The arbitrator must also follow the provisions of this Agreement as a court would. IF ANY PARTY COMMENCES ARBITRATION WITH RESPECT TO A CLAIM, NEITHER YOU, WE, OR THE INDEMNIFIED PARTY WILL HAVE THE RIGHT TO LITIGATE THAT CLAIM IN COURT OR HAVE A JURY TRIAL ON THAT CLAIM, OR TO ENGAGE IN PRE-ARBITRATION DISCOVERY, EXCEPT AS PROVIDED FOR IN THE APPLICABLE AAA RULES. FURTHER, YOU WILL NOT HAVE THE RIGHT TO PARTICIPATE AS A REPRESENTATIVE OR MEMBER OF ANY CLASS OF CLAIMANTS PERTAINING TO THAT CLAIM, AND YOU WILL HAVE ONLY THOSE RIGHTS THAT ARE AVAILABLE IN AN INDIVIDUAL ARBITRATION. THE ARBITRATOR’S DECISION SHALL BE FINAL AND BINDING ON ALL PARTIES, EXCEPT AS PROVIDED IN THE FEDERAL ARBITRATION ACT (the “FAA”). xxxxxxxxxxxxxxx the foregoing, you and we retain the right to pursue in small claims court (or an equivalent state court) any dispute that is within that court’s jurisdiction, so long as the disputes remain in such court and advance only an individual claim for relief. If either you or we fail to submit to binding arbitration of an arbitrable dispute following lawful demand, the party so failing shall bear all costs and expenses incurred by the other in compelling arbitration.\n\nRIGHT TO OPT OUT: If you do not want this Arbitration Agreement to apply, you must notify us within 30 calendar days after you sign the Agreement. You must send the notice in writing to our Service Provider at support@splitit.com. You must provide your name, address and state that you “opt out” of the Arbitration Agreement. Opting out will not affect the other provisions of this Agreement. If you opt out, it will apply only to this Agreement and not any other agreement you may have with us.\n\nTHIS ARBITRATION AGREEMENT DOES NOT APPLY TO YOU IF, AS OF THE DATE OF THIS AGREEMENT, YOU ARE A COVERED BORROWER UNDER THE FEDERAL MILITARY LENDING ACT. IF YOU WOULD LIKE MORE INFORMATION ABOUT WHETHER YOU ARE COVERED BY THE MILITARY LENDING ACT, IN WHICH CASE THIS ARBITRATION PROVISION DOES NOT APPLY TO YOU, PLEASE CONTACT OUR SERVICE PROVIDER AT SUPPORT@SPLITIT.COM\n\nProhibition of Class and xxxxxxxxxxxxxx Actions and Non-xxxxxxxxxxxxxx Relief. YOU AGREE THAT YOU MAY BRING CLAIMS AGAINST US OR INDEMNIFIED PARTY ONLY ON AN INDIVIDUAL BASIS AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE ACTION OR PROCEEDING. UNLESS BOTH YOU AND THE INDEMNIFIED PARTY AGREE OTHERWISE, THE ARBITRATOR MAY NOT CONSOLIDATE OR JOIN MORE THAN ONE PERSON’S OR PARTY’S CLAIMS AND MAY NOT OTHERWISE PRESIDE OVER ANY FORM OF A CONSOLIDATED, REPRESENTATIVE, OR CLASS PROCEEDING. ALSO, THE ARBITRATOR MAY AWARD RELIEF (INCLUDING MONETARY, INJUNCTIVE, AND DECLARATORY RELIEF) ONLY IN FAVOR OF THE INDIVIDUAL PARTY SEEKING RELIEF AND ONLY TO THE EXTENT NECESSARY TO PROVIDE RELIEF NECESSITATED BY THAT PARTY’S INDIVIDUAL CLAIM(S), EXCEPT THAT YOU MAY PURSUE A CLAIM FOR AND THE ARBITRATOR MAY AWARD PUBLIC INJUNCTIVE RELIEF UNDER APPLICABLE LAW TO THE EXTENT REQUIRED FOR THE ENFORCEABILITY OF THIS PROVISION.\n\nNOTICE: ANY HOLDER OF THIS CONSUMER CREDIT CONTRACT IS SUBJECT TO ALL CLAIMS AND DEFENSES WHICH THE DEBTOR COULD ASSERT AGAINST THE SELLER OF GOODS OR SERVICES OBTAINED PURSUANT HERETO OR WITH THE PROCEEDS HEREOF. RECOVERY HEREUNDER BY THE DEBTOR SHALL NOT EXCEED AMOUNTS PAID BY THE DEBTOR HEREUNDER.\n\nUsing your information. You will find a copy of our privacy policy on our website that you can review in connection with your purchase. As Splitit handles our payment requests and instructions for us, they will handle your data and we will pass information between us. You may obtain a copy of Splitit’s Privacy Policy by visiting their website at http://splitit.localsite/legals/splitit-privacy-policy/english/.\n\nWe may share information about our transactions and interactions with you with Splitit and other affiliated companies. We may also share information about our transactions and interactions with unaffiliated third parties in connection with providing this service to you including fraud detection services.\n\nHowever, the law may permit you to instruct us not to share this information with certain third parties. If you do not want us to share this information, you must notify us in writing or by email through our Service Provider at: support@splitit.com. If you email us a notification, you must include your name, address, and the last four digits of your card number used in this transaction so that such a request can be honored. Do not include your full card details in this email.\n\nxxxxxxxxxxxxxx. After completing your purchase, you will see some communications from us saying they are “powered by Splitit”. Splitit will send you an email following the completion of your purchase with details of how you can access information on your payments in a secure, password protected Portal. You are responsible for obtaining and maintaining all telecommunications, mobile, broadband, computer, hardware, software, equipment and services needed to access information about this Agreement or your payment method; view, save and/or print your account documents online; receive any messages or documents you have consented to receive electronically pursuant to the Electronic xxxxxxxxxxxxxx Disclosures and Consent, which is incorporated herein by reference; and for paying all related charges. Some of the communications between you and us or any of our affiliates, agents, assigns and service providers, may be monitored and recorded. By completing this transaction, you consent to this monitoring and recording and you further agree that we and our service providers may from time to time make calls and/or send text messages to you at any telephone number associated with your account, including wireless telephone numbers that could result in charges to you. The manner in which these calls or text messages are made to you may include, but is not limited to, the use of pre-recorded/artificial voice messages and/or automatic telephone dialing system. Your consent may be revoked at any time and by any reasonable means. You further agree that we or our service providers may send e-mails to you at any e-mail address you provide us or use other electronic means of communication to the extent permitted by law. We are not required to act on any instruction or message from you provided by fax, SMS/text, telephone voice mail, message service or answering machine. Whenever this Agreement or applicable law requires or allows you to give us written notice, we will not consider SMS/text or fax to be written notice. You must notify us promptly of any changes to your e-mail address, phone number, mailing address, or other contact information by using the Platform or by emailing our Service Provider at support@splitit.com.\n\nWho to contact about this Agreement. xxxxxxxxxxxx, you may require additional assistance in connection with this Agreement (for example, replacing payment method, number of outstanding xxxxxxxxxxxx, etc.). You may obtain information about your Agreement, including your remaining xxxxxxxxxxxx and your selected payment method through the Portal. You may also contact us through our Service Provider at support@splitit.com for support and information about this Agreement. If you have any questions about the goods and services you purchased under this Agreement, please contact our customer services department through the information provided on our website. We clarify that we hired Splitit to provide certain services and you do not have any agreement with them. Splitit cannot agree to any alternative arrangements other than to allow you to use a different card for the payment of any unpaid Instalments. In addition, Splitit does not have information regarding your relationship with the Issuer and accordingly cannot handle questions related to that arrangement.\n\nState-Specific Disclosures. If you are a resident of any of the following states or jurisdictions, the following provisions for your state will apply, and will supersede any conflicting provisions set forth in this Agreement:\n\nDistrict of Columbia: We certify that the information contained in the Agreement complies with the District of Columbia Municipal Regulations, Title 16, Chapter 1, if applicable.\n\nFlorida: Florida documentary stamp tax required by law has been paid or will be paid directly by us to the Department of Revenue.\n\nHawaii: This contract is covered by Hawaii’s credit sale law, and you have the rights of a buyer under that law. You also may have rights under other state and federal laws.\n\nMaryland: This Agreement will be governed by the laws of the State of Maryland. This Agreement shall be subject to the Credit Grantor Closed End Credit Provisions (Subtitle 10) of the Commercial Law Article of the Maryland Code.\n\nArizona, Delaware, Maine, Minnesota, Nebraska, Ohio, Oklahoma, and Wyoming. No provisions in this Agreement providing for the payment of attorneys’ fees, court costs or collection costs by you shall apply.\n\nNew Hampshire: If you prevail in any action involving this Agreement, we will pay your reasonable attorney’s fees. If you successfully assert a partial defense or set-off, recoupment or counter-claim, the court may limit the fees we can recover.\n\nNew Jersey: (1) The section headings of the Agreement are a table of contents and not contract terms. (2) You agree to pay reasonable attorney’s fees incurred by us in collecting any amount due and payable under this Agreement, in an amount not to exceed 20% of the first $500 owed and 10% of any amount owed in excess of $500, at the time this Agreement is referred to an attorney for collection who is not our salaried employee. (3) Provisions of this Agreement that refer to acts or practices that apply as permitted by, or except as prohibited by, applicable law are applicable to New Jersey residents only to the extent that such acts or practices are permitted by New Jersey or Federal law.\n\nOhio: Ohio laws against discrimination require that all creditors make credit equally available to all creditworthy customers and that credit reporting agencies maintain separate credit histories on each individual upon request. The Ohio Civil Rights Commission administers compliance with this law.\n\nxxxxxxxxxxxx: You agree that reasonable attorney’s fees and costs will be awarded to the prevailing party in any action on this Agreement, regardless of whether the action is instituted by us or you.\n\nVirginia: The service charge does not exceed 0% per annum, computed monthly.\n\nWisconsin: No provision of a marital property agreement, a unilateral statement under Wis. Stat. Ann. §766.59 or a court decree under §786.70 adversely affects our interest unless we, prior to the time the credit is granted, are furnished a copy of the agreement, statement or decree or have actual knowledge of the adverse provision when the obligation to us is incurred.\n\nENTIRE AGREEMENT. Oral agreements or oral commitments to loan money, extend credit, or to forbear from enforcing repayment of a debt may not be enforceable under applicable law. To protect you (as the buyer) and us (as the seller) from misunderstanding or disappointment, you and we acknowledge and agree that this written Agreement is a final expression of the agreement between you and us, and this Agreement may not be contradicted by evidence of prior, contemporaneous, or subsequent oral agreements of the parties. The terms of this Agreement may not be changed except in a writing signed by you and us. No change shall release any party from liability unless otherwise expressly stated in writing.\n\nIMPORTANT: You acknowledge that you had a reasonable opportunity to examine these xxxxxxxxxxxx Terms and Conditions; and that a legible and complete copy was delivered to you. Please notify us within thirty (30) days of the day you accept this Agreement if a complete copy is not delivered to you.\n\nNOTICE TO SHOPPER: (1) DO NOT APPROVE THIS AGREEMENT BEFORE YOU READ IT. (2) DO NOT APPROVE THIS AGREEMENT IF IT CONTAINS ANY BLANK SPACES. (3) YOU ARE ENTITLED TO AN EXACT COPY OF ANY AGREEMENT YOU SIGN. KEEP IT TO PROTECT YOUR LEGAL RIGHTS. (4) YOU HAVE THE RIGHT AT ANY TIME TO PAY IN ADVANCE THE REMAINING INSTALLMENTS DUE UNDER THIS AGREEMENT WITHOUT PENALTY.\n" type: string disclosure: description: Affirmative acceptance statement to present to the merchant. example: >- I have read and agree to Splitit Retail Installment Contract Terms and Conditions. type: string fees_url: description: Additional financing fee information. example: https://docs.whop.com/fees type: string policies: items: description: >- Financing policies to present alongside the contract before collecting acceptance. example: >- All Resolution Center cases for financed transactions will be automatically refunded. type: string type: array url: description: Source URL for the Splitit contract snapshot. example: https://whop.com/splitit-terms/ type: string version: description: >- Content fingerprint to pass as merchant_acceptance.terms_version when submitting. example: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx type: string required: - version - url - fees_url - disclosure - policies - content type: object V1ErrorResponse: properties: error: properties: code: description: >- Machine-readable reason for this specific refusal, such as `bank_warning_not_acknowledged`. Only present when the error carries one. type: string message: description: Human-readable error message. example: account_id is required type: string type: description: Machine-readable error code. example: bad_request type: string required: - type - message type: object required: - error type: object File: properties: blurhash: description: >- BlurHash placeholder for an image or video. Null when unavailable or removed by moderation. example: null type: - string - 'null' content_type: description: >- The original file's MIME type, preserved when removed by moderation, e.g. `application/pdf`. example: application/pdf type: - string - 'null' created_at: description: When the file was created, as an ISO 8601 timestamp. example: '2026-01-01T12:00:00.000Z' type: string duration_seconds: description: >- Audio or video duration in seconds. Null when unavailable or removed by moderation. example: null type: - number - 'null' filename: description: The original filename, including its extension. example: evidence.pdf type: - string - 'null' height: description: >- Image or video height in pixels. Null when unavailable or removed by moderation. example: null type: - integer - 'null' id: description: The file's ID, prefixed `file_`. example: file_xxxxxxxxxxxxxx type: string multipart_chunk_size: description: >- The byte size each part (except the last) must be. Present only on create, and only for multipart uploads. example: 5242880 type: - integer - 'null' multipart_upload_id: description: >- The ID of the multipart upload, passed back to `complete`. Present only on create, and only for multipart uploads. example: upload-id type: - string - 'null' multipart_upload_urls: items: $ref: '#/components/schemas/FileMultipartUrl' description: >- The presigned URL for each part. Present only on create, and only for multipart uploads. type: - array - 'null' object: description: The type of this object, always `file`. example: file type: string removed_by_moderation: description: >- Whether moderation removed the file. When true, `url` serves a replacement image; filename, size, and content type still describe the original file. example: false type: boolean size: description: The file size in bytes. `null` until the upload has finished. example: 9670 type: - integer - 'null' upload_headers: description: Headers to send with the upload PUT. Present only on create. example: {} type: object upload_status: description: Where the file is in its upload lifecycle. enum: - pending - processing - ready - failed example: pending type: string upload_url: description: >- Presigned URL to PUT the file's bytes to. Present only on create, and only for single-part uploads. example: >- https://whop-assets-example.s3.amazonaws.com/uploads/2026-01-01/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/application.pdf type: - string - 'null' url: description: >- A URL to download the file: a permanent CDN URL for public files, a signed expiring URL for private ones. Null until the upload has finished; a replacement image URL when removed by moderation. example: >- https://whop-assets-example.s3.amazonaws.com/uploads/audio/2026-01-01/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx type: - string - 'null' visibility: description: >- `public` files are served via an unsigned CDN URL; `private` files via a signed, expiring URL. enum: - public - private example: private type: string waveform_url: description: Audio waveform URL. Null when unavailable or removed by moderation. example: null type: - string - 'null' width: description: >- Image or video width in pixels. Null when unavailable or removed by moderation. example: null type: - integer - 'null' required: - object - id - filename - content_type - size - url - removed_by_moderation - upload_status - visibility - created_at - width - height - blurhash - duration_seconds - waveform_url type: object Money: properties: amount: description: >- The amount in major units, as an exact decimal string — `"10.00"` is ten dollars. A string so no float rounds it in transit. example: '-1234.56' type: string currency: description: Three-letter ISO 4217 currency code, lowercase. example: usd type: string decimals: description: >- How many decimal places the amount CARRIES — the precision the charge itself runs at. example: 2 type: integer display_decimals: description: >- How many decimal places to SHOW. Usually equal to `decimals`, and deliberately not always: COP is charged in centavos but written in whole pesos, so it is `2` and `0`. Format the number in your own locale using this. example: 2 type: integer required: - currency - amount - decimals - display_decimals type: object FileMultipartUrl: properties: part_number: description: The 1-based index of this part within the multipart upload. example: 1 type: integer url: description: The presigned URL to PUT this part's bytes to. example: >- https://whop-assets-example.s3.amazonaws.com/uploads/2026-01-01/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/application.pdf type: string required: - part_number - url type: object responses: Unauthorized: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Unauthorized Forbidden: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Forbidden NotFound: content: application/json: schema: $ref: '#/components/schemas/V1ErrorResponse' description: Resource not found securitySchemes: accountApiKeyOrAccountTokenOrOauthTokenAuth: bearerFormat: auth-scheme description: >- An Account API key, an account access token, or a user OAuth token. Prepend the key or token with `Bearer`, for example `Bearer ***************************`. See [Auth & API keys](/developer/guides/auth-scoping) for how to get each one. scheme: bearer type: http ```` ## Related topics - [Create Financing Application](https://docs.whop.com/api-reference/financing-applications/create-financing-application.md) - [Submit Financing Application](https://docs.whop.com/api-reference/financing-applications/submit-financing-application.md) - [Update Financing Application](https://docs.whop.com/api-reference/financing-applications/update-financing-application.md)