Forge64 apps can take payments in two ways: with Forge Payments, which has seller verification and payouts to your bank account built in, or with your own payment account, where you keep your own payment provider and Forge64 stays out of the money. Status: rolling out.
Which one to pick
| Forge Payments | Your own payment account | |
|---|---|---|
| Who is paid | Forge64 pays you out to your bank account | Your provider pays you, directly |
| What Forge64 needs from you | Identity and bank details, once | A secret key and a webhook signing secret |
| Where the money sits | Your Forge Payments balance | Your own provider's balance |
| Forge64's fee per sale | One all-in fee, see Fees | None |
| Which plans | Free, Pro, Business | Enterprise |
| Selling a subscription | Yes, on the newest apps | Yes |
| Selling usage credits | Not yet | Not yet |
Pick Forge Payments unless you are on the Enterprise plan and want the money to land in your own provider's account from the first sale.
Forge Payments
How it works
- Open the connect settings page in your dashboard (
/dashboard/settings/connect) and start onboarding. You confirm your identity and add your bank account on the onboarding pages Forge Payments shows you. - When your account is confirmed able to accept charges, your app's checkout is switched on. Checkout is refused until then.
- Customers pay in your app. The money is paid out to your bank account. Forge64 does not hold your funds.
When you get paid
Payouts go out once a week, on Friday, for sales that have cleared a 7-day settlement delay. A sale is paid on the first Friday after its delay ends, so the wait is typically one to two weeks. In some countries the delay counts business days, which can add a few calendar days.
Why: refunds and chargebacks (card disputes) can arrive days after a sale. The delay keeps that money in your Forge Payments balance until the risk window is mostly over, so a refund or dispute is taken from funds that are still there instead of leaving your balance negative. Forge64 does not hold your funds: they sit in your own Forge Payments balance and are paid to your bank account on that schedule. The schedule is the same for every seller and is not something you set.
Your bank may take a further 1 to 3 business days to show the deposit. Instant payouts are not available.
Your own payment account
Available on the Enterprise plan. You paste your own provider's secret key into your app's settings; Forge64 stores it encrypted and never sends it back to you, and your app never holds it in the browser.
- In your dashboard, open the app's Payments settings and paste your secret key (or a restricted key) and the signing secret from your provider's webhook settings.
- Turn the app over to your own account. Until you do, the app takes payments through Forge Payments.
- Point your provider's webhook at the address Forge64 shows you in the same panel. Forge64 verifies the signature with your signing secret, so only your provider's events are accepted.
- Your app learns that a sale was paid by reading the checkout back from Forge64 (the generated app's payment SDK does this for you) or by polling it from your own server.
What this changes:
- The fee is zero. Forge64 does not take a fee on a sale made through your own account. On Enterprise, any negotiated fee is invoiced separately, monthly, rather than taken from each sale.
- Your provider's rules apply. Fees, disputes, refunds, tax and payout speed are your provider's, not Forge64's.
- Refunds are made from your dashboard against your own account.
- Only one-time sales go through this route. Subscriptions through your own account are set up by the app itself (see below).
Selling a subscription
- On Forge Payments: apps built with the newest app runtime can sell subscription plans. The plan price, currency and billing interval come from the app's own configuration, the customer sees a checkout page, and the app grants and withdraws the plan's access when the subscription starts, renews or is cancelled.
- On your own payment account: the generated app creates the subscription checkout against your own provider and receives the subscription events on its own webhook route, so the app grants access itself.
Either way the customer can cancel from your provider's customer portal, and the app sees the cancellation on the next event.
Selling usage credits
Not available yet. Usage-based billing (selling a number of credits and charging for what the customer actually uses) is not implemented on either route. Today's usage meters are Forge64's own, for Forge64's hosting and AI, and they are not a product you can sell inside your app.
Fees
On Forge Payments, one all-in fee per sale, card processing included: Free 13% + 30¢, Pro 9% + 30¢, Business 7% + 30¢, Enterprise per contract. Current figures are on the pricing page.
Worked example, a $100 sale on Pro: the fee is $9.30 (9% of $100 plus 30¢), so $90.70 reaches you before any refund. The smallest charge an app can take is $1.00.
On your own payment account, Forge64 takes no fee per sale.
Where sellers can be paid
Sellers in the United States are paid out domestically. Sellers in the United Kingdom, Canada, Switzerland and the European Economic Area can onboard for cross-border payouts. Other countries are coming soon. See payout countries.
Tax
Forge Payments is not the seller of record and does not file or remit sales tax or VAT for you. You stay responsible for the tax on your sales. On your own payment account, everything about tax is between you and your provider.