Answers, written from what the product actually does.
Every guide here was checked against the code that implements it. If one disagrees with the product, that is a bug in the guide — tell us and we will fix it.
Getting paid
Connecting Stripe, what EmbPay charges, and when the money reaches you.
- Connecting your Stripe accountConnect your own Stripe account so sales settle directly to you, and understand why a connected account is not always ready to charge yet.
- Fees, payouts and who holds your moneyEmbPay takes 0% of every sale on every plan. Here is exactly who charges what, who is the merchant of record, and when Stripe pays you.
Selling
Pricing models, currencies, order bumps, upsells and running a rehearsal.
- Which currencies you can sell inThe product form offers five currencies and the API accepts any Stripe-supported code. Prices are never converted automatically based on where your buyer is.
- Subscriptions, split-pay and pay-what-you-wantOffer up to six ways to pay for one product: one-time, subscription, a fixed number of renewals, split-pay instalments or a buyer-chosen price.
- Order bumps and one-click upsellsAdd up to five bumps at checkout and a branching upsell funnel after the payment, on every plan including free.
- Rehearsing a purchase with test modeSwitch a product to test mode to walk through your own checkout end to end without a real charge, and know exactly what still happens for real.
Delivering
Getting the product to the buyer: files, licence keys and subscriptions.
- Delivering files with expiring linksUpload a file up to 500 MB and EmbPay delivers it as a private, expiring link in the buyer's confirmation email and customer hub.
- Selling software with licence keysIssue a licence key on purchase, cap how many machines can activate it, optionally expire it, and verify it from your own software.
- What buyers can do for themselvesBuyers reach their purchases through an emailed link, with no account or password, and can cancel or resume a subscription themselves.
After the sale
Refunds, failed payments, and what buyers can do for themselves.
Developers
API keys, webhooks and verifying licences from your own software.
- API keys and rate limitsCreate an API key on the Pro plan, authenticate with a bearer token, and stay inside 100 requests per minute per key.
- Connecting an AI assistant with the MCP serverPoint an MCP client at EmbPay's server with your API key and ask it about sales, create products and checkout links, or refund an order you confirm.
- Receiving webhooks and verifying signaturesReceive seven order and subscription events at your own https endpoint, verify the signature, and understand the retry schedule.
- Verifying a licence from your softwareCall one public endpoint to check whether a licence key is valid, with no API key needed and browser requests allowed.
Building on the API?
The API reference covers endpoints, authentication and webhook payloads, and the JavaScript SDK covers embedding checkout on your own site. For anything else, email support@embpay.com.