Legal
Flint Platform Agreement
Version 2026-11-16. Effective November 16, 2026.
1. Overview
This Flint Platform Agreement ("Agreement") is between Flint Pay Inc. ("Flint," "we," "us," or "our") and the business that owns a Flint partner app ("you"). It applies when you ask Flint to approve your app as a platform, so that it can charge platform fees, run merchants' live onboarding, create merchants, or send payment splits (the "platform capabilities").
You accept this Agreement by accepting version 2026-11-16 of the platform terms for your app, in the Flint Dashboard or through the API. Flint records who accepted, when, and the IP address and user agent of the request. Whoever accepts confirms they have authority to bind your business. Accepting the placeholder version 2026-11-01, which had no published text, is not accepting this Agreement.
This Agreement adds to the Terms of Service and the Recipient Terms of Service, which still apply to your own Flint merchant account. Where this Agreement says something different about the platform capabilities, this Agreement controls.
The percentages, periods, and limits below are Flint's defaults. Once Flint approves or limits your app, its platform object in the API and its Platform tab in the Dashboard show the ones Flint set for you, and those apply.
2. Approval
Flint reviews your app once all of these are true:
- The Flint merchant account that owns the app has finished live onboarding, including a payout bank account. Flint pays your platform fees to this account.
- You have given Flint a platform profile: your product, the merchants you serve, the merchant count and volume you expect, how you onboard and monitor merchants, a support contact, and your website.
- You have accepted this Agreement.
Flint then approves your app, approves only some of the capabilities it requests, or rejects it. Flint decides at its discretion and can reopen a rejected review. A capability you request after approval stays off until Flint approves it.
Keep your profile accurate, and update it when your product, the merchants you serve, or your volume changes materially. If a requirement stops being met, for example your account can no longer receive payouts, every platform capability turns off until you fix it.
You can build in test mode before approval. Until Flint approves merchant creation, test signups work only for your own team's email addresses.
3. Your Merchants
Each merchant your app serves is its own Flint merchant, with its own agreement with Flint. Its sales settle to its own Flint balance and bank account, and it pays Flint's fees directly. You never hold a merchant's money, and the merchant keeps its account if it leaves you.
You agree to:
- Act for a merchant only within the permissions it approved, and only while your app is installed on its account.
- Serve only businesses Flint's payment processor allows. You may not onboard a merchant whose business is on Stripe's Restricted Businesses list, or one you know or suspect is fraudulent.
- Tell merchants accurately what your product does and what you charge them, including your platform fee.
- Onboard and monitor your merchants as your platform profile describes, and support them for your product.
- Confirm that a person manages a merchant before you open a verification session or an onboarding link for them.
- Tell Flint promptly when you learn of fraud, a compromised credential, or unusual refunds or disputes at one of your merchants.
4. Platform Fees
A platform fee is an amount you take from a payment your app creates for a merchant with a partner app token. It comes out of the payment, the merchant pays it in addition to Flint's fees, and Flint takes no share of it.
- The cap. Each merchant approves a platform fee cap when it installs your app, separately for test mode and live mode. A fee never exceeds the cap that merchant approved. Flint refuses a fee above the cap when you create the payment, and lowers the fee to the cap if the amount collected changes before the payment completes.
- Changing the cap. A cap you lower or remove applies to every merchant at once. A cap you raise applies to a merchant only after that merchant approves it.
- Flint's fees come first. If Flint's fees plus your fee would reach the amount collected, Flint lowers your fee.
- Payments without your fee. If the merchant has disconnected your app or no longer approves a cap, or your platform fee capability isn't active in live mode, the payment goes ahead without your fee. A buyer's payment never fails because of your fee.
- Where fees apply. Only the requests listed in the platform fees guide accept a fee. Subscriptions, invoices, and payment links don't.
- Refunds and disputes. You keep your fee when the merchant refunds a payment or a buyer disputes it. You can choose to return the fee, or the refunded share of it, when you create the refund.
- Returned payments. When Flint or its payment processor returns the fees on a payment, for example because a bank debit failed after it was collected, your fee on that payment goes back to the merchant in the same proportion.
5. Payouts of Your Fees
Flint records each fee on your platform fee ledger when its payment succeeds. A fee becomes available once Flint has matched it with its payment processor and the processor has made the funds available to Flint. Flint never pays you a fee it hasn't collected.
In live mode, Flint pays your available fees into your own Flint merchant balance once a day, when at least $1.00 is available. Your merchant account's payouts then take the money to your bank under the Recipient Terms of Service. In test mode, payouts run every hour with a one-cent minimum.
Payouts of platform fees wait while Flint has paused your platform, while your merchant account can't receive payouts, or while Flint has stopped payouts to protect its own balance with its payment processor, including when that balance can't cover them. Flint pays waiting fees in a later run.
6. Withheld Fees
Flint withholds part of each platform fee as a reserve against losses on your merchants (Section 7).
- Share. 20% of each fee by default, rounded to the nearest cent.
- Release. Flint releases a withheld amount at 00:00 UTC, 120 days after the end of the UTC day the fee was collected. A fee collected at any time on November 9, 2026 (UTC) releases at 00:00 UTC on March 10, 2027. Released amounts join your available fees and go out with the next payout. An amount whose funds aren't available to Flint by then releases once they are.
- Your terms. Flint sets your share and hold period when it approves your app, and can change them later: the share from 0% to 100%, and the period from 0 to 365 days. Your app's
platform.reserveshows them. A change applies only to fees collected after it. - Returned fees. Returning a fee releases its proportional share of the amount still withheld from it. Flint rounds the cumulative share to the nearest cent, so returning the whole fee releases its remaining hold. Amounts already released or used to cover losses cannot be released again.
- Interest. Flint pays no interest on withheld fees.
In test mode, withheld amounts release one day after the end of the UTC day the fee was collected, so you can test a release.
7. Losses
Flint carries the losses on its merchants, yours included. Your withheld fees cover the losses on your merchants first.
A loss is the part of a lost dispute, or of a refund Flint funded, that Flint could not recover from the merchant after it stopped trying, including by holding the merchant's payouts and debiting its bank account. A loss is never more than the dispute or the refund.
A loss is yours when:
- the payment that caused it carried your platform fee; or
- you created the merchant through a merchant signup, and the payment was created in live mode while the install from that signup was active in live mode and had never been revoked.
If the payment carried another platform's fee, the loss is that platform's and not yours. A loss is attributed to one platform at most.
Flint covers a loss that is yours in this order:
- From your withheld fees, taking the amounts due for release soonest first. Only amounts whose funds are available to Flint count.
- While Flint has paused your platform, from your available live fees that haven't been paid out, never taking that balance below zero.
- Flint carries the rest and doesn't bill you for it. This limit doesn't apply to a loss caused by your fraud or by your breach of this Agreement.
Each amount your fees cover appears on your platform fee ledger as loss_coverage, linked to the dispute or the refund. If Flint later recovers money on the loss, the recovery repays Flint first. Once recoveries exceed what Flint carried, Flint returns your coverage as loss_coverage_reversal.
8. Fees You Return After Payout
When you return a fee, Flint releases its proportional share of the amount still withheld and deducts the rest from the fee's pending or available balance. If Flint had already paid that fee out to you, or its withheld amount was used to cover losses, your available balance can go negative. Your next platform fees and your next releases of withheld fees then repay it before Flint pays anything out. If the balance is still negative when this Agreement ends, you owe Flint that amount.
9. Limits
Flint sets two limits when it approves your app:
- Live merchants. 25 by default. A merchant counts from the first time you use a platform capability on it in live mode: collecting a fee, running its onboarding, or first connecting in live mode to a merchant you created through a signup. It stops counting when your app's live access to it is revoked.
- Monthly volume. $100,000 by default. It counts the captured amounts of live payments that carried your platform fee, in each calendar month (UTC).
Your app's platform.limits shows your limits and your usage. Flint can change your limits at any time.
These two limits are soft. Flint never refuses, lowers, or delays a payment, a fee, or an onboarding step because of either one. When you approach or cross one, Flint is alerted and may raise the limit, turn off a capability, or pause your platform (Section 10). The caps on merchant signups in Section 11 are separate, and Flint does refuse a signup over one of them.
10. Limiting, Pausing, and Rejecting
Flint may turn off a platform capability, pause your platform, or reject your app at any time to manage risk. Reasons include crossing a limit, rising refunds, disputes, or losses on your merchants, a profile that is no longer accurate, a breach of this Agreement, and a requirement of law or of Flint's payment processor. Your app's platform object shows its status and why each capability is inactive, and Flint sends a partner_app event to your webhook endpoints when it decides.
While Flint has paused your platform:
- Every platform capability is off in live mode. Payments you create go ahead without your platform fee, and live onboarding through your app and live merchant signups are refused.
- Flint holds payouts of your live platform fees. Withheld fees still release on schedule, into the balance Flint is holding.
- The fees Flint is holding can cover losses, as Section 7 describes.
Your merchants keep taking payments, your app stays installed, and test mode keeps working. When Flint resumes your platform, the capabilities it had approved and your payouts come back.
Rejecting your app or turning off a capability doesn't take away fees you already earned. They stay subject to Sections 5 to 8.
11. Merchants You Create
With the merchant creation capability, your app can create a Flint merchant for a business owner from your own signup form.
- Flint creates the merchant only when the owner enters the code Flint emailed them. Don't enter a code, or accept Flint's merchant terms, for an owner. Show the owner Flint's merchant terms, and send Flint the owner's own acceptance with the IP address and user agent of the owner's browser.
- Sign up only people who asked you to. Flint caps signups: 1,000 a day for your app by default once Flint approves merchant creation, and 20 a day before that. Flint also limits how many codes it emails to one address and how many wrong codes it accepts. Flint refuses a signup, a code, or an attempt over a cap.
- The merchant belongs to its owner. The owner has a Flint login from the start and can use it at any time.
Emails. While the install from your signup manages a merchant, the links in Flint's emails about finishing verification, and the payment processor's notification links, lead to your app's merchant_action_url. They do so only once Flint has reviewed your website, and in live mode only while your merchant onboarding capability is active. Emails about risk, reviews, disputes, payouts, and balances lead to Flint. A link carries no authority: sign the person in yourself and confirm they manage the merchant.
Your merchant action URL. Its registrable domain must match the website in your platform profile. Flint emails every change of the URL to the owners and admins of your merchant account. After Flint first approves or limits your app, a change of the URL or of your website to another registrable domain takes effect 72 hours later, or when a pause of your platform ends if that is later. Until then, emails keep leading to the previous URL. A change within the same registrable domain applies at once. If you clear the URL, emails lead to Flint, and new signups are refused until you set one.
When managing ends. The first time that install is revoked, by the merchant, by you, or because you delete your app, the email links return to Flint for good, and Flint emails the owner once that they can sign in to Flint. Installing your app again doesn't bring the links back.
12. Payment Splits
A marketplace that collects payments as the seller of record can declare payment splits on its app, to send part of a payment to sellers that installed the app.
- Seller terms. You publish your terms for sellers at the
seller_terms_urlyou declare, and keep them there. They are your agreement with your sellers, and Flint isn't a party to them. Flint's consent screen tells each seller that you take back the seller's share when you refund a sale, lose a dispute, or a payment fails. Your terms must not say otherwise. - Approval. Each seller approves receiving split funds under those terms when it installs your app. If you change the URL, sellers that already approved stay on the terms they approved. If you remove the declaration, every approval ends at once.
- Your payments. A payment you collect as the seller of record is your own payment under the Recipient Terms of Service. You are responsible for its refunds, disputes, and returns in full, including any part you sent to a seller.
Flint doesn't accept splits on payments yet. Before it does, Flint will publish a new version of this Agreement with the rules for sending, reversing, and recovering split funds.
13. Disconnecting
A merchant can disconnect your app at any time, in the Dashboard or through the API. You can disconnect a merchant too. When an install is revoked:
- Your access to that merchant ends at once. So do the events Flint forwards to you for it, and every API key and webhook endpoint linked to the install. Installing again doesn't restore them.
- You stop calling the API for that merchant, revoke any other key of the merchant's that you hold, and delete any other webhook endpoint you registered on its account.
- Payments that haven't completed go ahead without your platform fee. Fees you already collected stay yours, subject to Sections 5 to 8.
- The merchant stops counting toward your live merchant limit.
- Losses on payments made before the disconnect can still be yours under Section 7.
Revoking one mode, test or live, ends only that mode. To delete your app, revoke its active installs first.
14. Data
- Merchant and buyer data. Use the data you reach through an install only to provide your product to that merchant, within the permissions it approved. Don't sell it. Protect it with reasonable security, follow the data protection laws that apply to you, and tell Flint and the merchant promptly if it is exposed.
- Credentials. Keep your app's credentials and tokens secret. You are responsible for what is done with them. If one is exposed, replace it and tell Flint.
- After a disconnect. You have no further access to that merchant through Flint. Data you already hold stays subject to your own agreement with the merchant and to the law.
- What you give Flint. Flint uses your platform profile, your acceptance record, and your usage to review and monitor your platform and to run the platform capabilities. When you sign up an owner, you give Flint their name, email, IP address, and user agent, and you confirm you are allowed to. Flint's Privacy Policy describes how Flint handles personal data.
- What Flint shows others. Merchants see your app's name, the permissions and platform fee cap you request, and your seller terms link. Flint's emails to merchants you created name your app and show the host of your website or of your merchant action URL.
15. Term and Termination
This Agreement starts when you accept it and lasts until it ends.
- You can end it at any time by deleting your app or by contacting Flint.
- Flint can end it with 30 days' notice. Flint can end it at once if you breach this Agreement or the Terms of Service, if Flint reasonably suspects fraud, if the law or Flint's payment processor requires it, or if your Flint merchant account closes.
When this Agreement ends, your platform capabilities turn off. Flint still pays the fees you earned before then under Section 5. Your withheld fees keep covering losses on payments made before the end, and release on their schedule, under Sections 6 and 7. You pay any negative balance under Section 8. Sections 4 to 8, 13, 14, and 17 survive.
16. Changes to This Agreement
Flint may publish a new version of this Agreement. Each version is named by its date, and your app's platform.current_terms names the current one.
- Flint announces a new version at least 30 days before it is required, unless the law or Flint's payment processor requires the change sooner. Your app's
platform.current_termsshows the date. Until then, the version you accepted still applies. - A new version applies to you only when you accept it. If you haven't accepted it by the date it is required, your platform capabilities turn off until you do.
A change Flint makes to your own share, hold period, or limits under Sections 6 and 9 is not a change to this Agreement.
17. Liability and Governing Law
The indemnification, limitation of liability, and disclaimer of warranties in the Terms of Service apply to this Agreement. This Agreement is governed by the laws of the State of Delaware, and any dispute under it is resolved in the state or federal courts located in Wilmington, Delaware, as the Terms of Service provide.
18. Contact
If you have questions about this Agreement, contact us at help.withflintpay.com.