How sellers get paid on Forge64

The seller completes hosted onboarding (identity and bank details go to the payment processor, not Forge64). A buyer's checkout is created on behalf of the seller with an application fee for Forge64. The full charge is credited to the seller's balance and the fee moves to Forge64's platform account. Payouts to the bank are scheduled by the processor.

• Rolling outDestination charges with the seller as business of record; the processor handles identity verification, custody of the seller's balance and bank payouts.
• BuiltForge64 holds no seller funds and has no balance or payout code of its own. A held-funds model (collecting money first and paying out later) is not built and would need licensing.
• BuiltCheckout is refused until the seller's account can accept charges.
• BuiltA minimum platform fee per sale and a minimum charge amount.

• Rolling outRefunds are ownership-checked, reverse the transfer to the seller, require a request identifier to prevent double refunds, and have a daily cap.
• Rolling outA dispute (chargeback) is recorded, alerts the owner, and the transfer to the seller is reversed. The processor's dispute fee stays with the platform under the current policy.
• BuiltForge64 is liable to the payment processor for refunds and disputes the seller cannot cover. A seller with a negative balance can therefore be pursued by the processor; this is the cost of the destination-charge model.

Forge Payments charges one all-in fee per sale, with payment processing included and no separate processor fee added on top. The fee depends on the plan: Free 13% + 30¢, Pro 9% + 30¢, Business 7% + 30¢, Enterprise per contract. Forge64 plan prices and allowances are on the pricing page and are not repeated here.

• BuiltAll-in fee per sale by plan, read from the plan catalog: Free 13% + 30¢, Pro 9% + 30¢, Business 7% + 30¢, Enterprise per contract.

Forge Payments works in the countries where the payment processor's connected-account product is available to the seller. Selling in other countries, and through a merchant-of-record provider, is on the Roadmap.

• Rolling outSellers in countries supported by the payment processor's connected accounts.
• RoadmapPayouts for sellers in countries the processor does not support, through an alternative provider.
• RoadmapRecurring subscriptions sold by an app through Forge Payments. Subscriptions currently need the seller's own processor account.

Forge64's own plans are billed through a payment processor. Every paid meter has a hard cap and an owner-set overage spend cap. Usage reporting for overage is switched off by default.

• BuiltPlan billing through hosted checkout, with hard caps and spend caps on every meter.
• Rolling outMetered overage reporting to the billing system.

Who holds the money when someone buys from an app built on Forge64?

The payment processor does. The charge lands in the seller's own balance and the processor pays it out to the seller's bank. Forge64 never holds seller funds and collects only a platform fee.

Do I need my own payment account to get paid through Forge64?

You complete hosted onboarding, which creates a connected account for you, so you do not need to set one up separately first. Sellers in countries the processor does not support are not covered yet.

What does Forge64 charge on payments?

One all-in fee per sale, processing included: Free 13% + 30¢, Pro 9% + 30¢, Business 7% + 30¢, Enterprise per contract. The fee is set by the plan of the account that owns the app.

Who is responsible for refunds and chargebacks?

The seller is the business of record. Refunds reverse the transfer to the seller, and disputes reverse it too. Because Forge64 is the platform, it is liable to the processor for amounts the seller cannot cover.

Is Forge Payments live?

It is built and tested in the processor's test mode. It becomes available for live money after the platform's payment settings are completed, so check with Forge64 before relying on it.