Programme management
Choose a programme management model.
Stripe offers two operating models for issuing: Stripe programme management and processor-only. Each comes with unique advantages and requirements, but both allow you to use Stripe for your issuing programme. This guide covers the differences between the two models so you can decide the best option for your business.
Overview
Stripe programme management allows you to take advantage of Stripe’s existing partner relationships, processes, tools, and expertise to remove the complexity from your integration. With processor only, you’re responsible for managing your programme, including regulatory requirements, compliance, Know Your Customer (KYC), anti-money laundering (AML), licensing, and more. The table below outlines the main differences between each model:
| Capability | Stripe programme management | Processor only |
|---|---|---|
| Compliance management | Stripe | You |
| Regulatory requirements | Stripe | You |
| Anti-money laundering (AML) | Stripe | You |
| Bank management | Stripe | You |
| Know Your Customer (KYC) | Stripe | You |
| Fraud management | Stripe | You or Stripe |
| Card management | Stripe | Stripe |
| Network processing | Stripe | Stripe |
| Ledger | Stripe | You |
| Underwriting & capital | You | You |
| Billing & repayments | Stripe | You or Stripe |
| Servicing & collections | Stripe | You or Stripe |
Stripe programme management
In this model, Stripe handles all regulatory, compliance, KYC, AML, fraud management, and manages the bank relationship on your behalf. You can control many aspects of your issuing programme using our APIs. You’re responsible for:
- Documenting your use case and product for approval by Stripe
- Funding your programme
- Integrating with the Stripe API or using the Dashboard to create cards and operate your programme
- Submitting physical and digital card artwork for approval by Stripe
- Submitting marketing material for approval by Stripe
Processor only
Use this model if you have your own licences or bank relationship, where applicable. You can still use the Stripe API and authorisation systems, but you have more responsibility compared to Stripe programme management, namely:
- Regulatory requirements for all localities where you operate
- Acquiring and maintaining licences or a bank relationship, where applicable
- Compliance
- KYC
- AML
- Fraud management
- Managing disputes raised by your cardholders
- Licensing a BIN
- Funding your programme
- Maintaining a ledger and making sure it’s correct and reporting on it to the regulator or bank
- Integrating with the Stripe API or using the Dashboard to create cards and operate your programme
- Submitting physical and digital card artwork for approval by the network and bank partner, where applicable
- Submitting marketing material for approval by your legal team
Choosing a model
If you’re just starting out with issuing, we recommend Stripe programme management. It simplifies your programme and requires fewer resources to operate it. If your goals change as your business changes, you can transition to the Stripe processor model later.
For businesses with established operations, legal, compliance, and financial services personnel, a direct relationship with a bank might benefit you. The processor-only model is for businesses who have the resources to take on the increased responsibilities and want more control over their issuing programme. This model works if you want to use the Stripe API, and if you can manage the operational burden. It also works if you want a bank partner not supported by Stripe, or have licensing or compliance needs Stripe can’t support.