Evaluating OpenPartner

Pricing and fees

• Revshare: 3% of partner-attributed revenue, with no monthly fee.
• Flex: $49 a month plus 1.5% of partner-attributed revenue.
• Higher commissions and bounties: if you pay partners more than 30%, or flat bounties and bonuses instead of a share of sales, the fee is 10% of the commission on Revshare (5% on Flex) when that's higher. Up to 30% commission you pay exactly the revenue rate.
• The marketplace (the OpenPartner Network) is included in hosted plans, with no extra fee on any partner.
• No payout fees: no setup fee, deposit or prefunding, and no fee on what you pay partners.
• Refunds and chargebacks reduce the fee as the partner's commission on them is reversed or clawed back. If the sale was already invoiced, the difference is credited on a later invoice.
• Getting started: signing up doesn't ask for a card. You get a 14-day trial and choose a plan before approving your first partner. Usage is billed monthly in arrears, by card, or by monthly invoice payable by card or bank transfer where we've agreed it.

See Pricing and the worked example What one sale costs you, end to end.

Paying partners

• You pay your partners directly, by PayPal, bank transfer or any method you use, then mark each payout paid in the dashboard or by API. Stripe Connect isn't required.
• OpenPartner calculates what each partner is owed and records every payout. It keeps partners' payout details encrypted, and can produce a PayPal batch file for you to upload to your own PayPal account.
• We never hold, receive or send that money, and we charge no transfer fee on it.
• You set the payout cadence (weekly, every two weeks, monthly or by hand), an optional minimum payout, and a holding period before commissions become payable.

See the Terms (section "Payouts to partners") and Getting paid.

Attribution

• Window: set per program, from 1 to 365 days (default 60), measured from the partner's click to the conversion.
• Renewals: the customer's first attributed conversion has to fall within the window. With "Renewals stay with the partner who earned the customer" on (the default), later invoices then keep their partner after the window closes, while the partner is still in your program.
• Identify: at signup, your app or server links your user ID to the click. After that, events are attributed from the user ID, with no cookie needed, across devices. Your user ID can be pseudonymous, such as a salted hash.
• Cookies and consent: the click reaches your site as a cref URL parameter. Our link router also sets a 90-day cookie when the click happens; on our hosted tracking links a browser won't set it for your own domain. On your site, the browser SDK is optional: you can call identify from your server instead, and wait for consent before loading anything.

See Attribution window, How attribution works and Cookies + cref.

Integration

• Server API: identify at signup, then report paid invoices and refunds. Use a scoped API key with only the events:write permission. Send each paid invoice with its invoice ID, and each refund with its own refund ID. A retry with the same ID and the same values is never counted twice.
• Stripe App: connect your own Stripe account and OpenPartner reads invoices, renewals, refunds and promotion codes from it.
• Script tag or SDK: captures the click on your site and hands it to Stripe Payment Links and Checkout.

See the API overview, Events and refunds, the API reference, the Stripe App and SDK install.

Data, privacy and security

• DPA: our Data Processing Addendum is the Common Paper DPA 1.1 with the EU Standard Contractual Clauses and UK Addendum. It forms part of the Terms, with no signature needed; countersigned copies are available on request.
• Sub-processors and their locations are at openpartner.dev/subprocessors. We email 30 days before adding or replacing one. Data is hosted in the US (DigitalOcean, New York).
• Retention: your program data is kept while your account is open. After you close it, you can restore it for 30 days; then it's deleted, and backups expire about 7 days later. We keep our own billing records for 7 years and sanctions-compliance records for 10. See the Privacy Policy.
• Export: everything in the documented export, any time, as CSV, JSON or SQL.
• Security: payout details and integration credentials are encrypted at rest, and API keys and sessions are stored as hashes. We don't hold a SOC 2 or ISO 27001 certification yet, and we answer security questionnaires on request. See Security.
• Where we operate: we don't serve brands or partners located in Cuba, Iran, North Korea, Russia or the occupied regions of Ukraine. We may also decline other countries, as the Terms describe.

Questions

• Sales and general: [email protected]
• Privacy and the DPA: [email protected]
• Security: [email protected]

If you have several questions, send them in one email, or ask for a call.