Partner requirements and best practices

Stay in good standing as a Stripe Partner by meeting all of Stripe's technical and business requirements for your integration type.

Integration-specific benchmarks

Select the type of integration you are building to see Stripe’s corresponding requirements and recommendations.

Your platform integration should meet these requirements:

Have a minimum of 5 active connected accounts
Create a Stripe-specific landing page that explains your integration (e.g., Xero example)
Provide required partner listing links
Adhere to Stripe brand and trademark guidelines. For example, while you may reference your partnership with us, or note that your offering works “with Stripe” or “for Stripe”, or is “powered by Stripe”, you may not use “Stripe” as part of the name of your offering (including, for example, in your domain name, social media handle, app name, etc.).

Collect zip code, name, and email when tokenizing cards to protect against disputes
Listen to webhooks events to stay informed about payments events
- Integrations using Payments should listen to events like payment_intent.succeeded, payment_intent.payment_failed or checkout.session.completed
- Integrations using Billing and Invoicing should listen for events relevant to user’s invoices from invoice.created to invoice.paid
- Avoid listening to all events on webhook endpoints
Include measures to prevent card testing when collecting payment information