Some regions require additional configuration to be compliant with regulations for co-badged cards. To make sure your integration is compliant with the latest regulations, we recommend you always upgrade to the latest version available.
Requirements for integration
Use the table below to find the minimum requirement for your integration to be compliant with co-badged card regulations:
| Integration type | Requirement |
|---|---|
| Checkout API-only | Find out how to identify card brands so you can make your front end integration compliant with the regulations. |
| Custom card integration with encryption | Find out how to make your integration compliant. |
| Web Drop-in or Components | Use v6.21.0 or later. |
| iOS Drop-in or Components | Use v5.19.1 or later. |
| Android Drop-in or Components | Use v5.13.0 or later. |
| React Native Drop-in or Components | Use v2.7.0 or later. |
| Flutter Drop-in or Components | Use v1.5.0 or later. |
| Salesforce Commerce Cloud SFRA cartridge | Use v25.5.0 or later. |
| Adobe Commerce plugin | Use v10.2.0 or later. |
| Classic API-only | Make sure that your integration satisfies the regulation requirements. |
If you are using our Drop-in or Components with one of the versions listed above with Checkout API v71, your integration is compliant out-of-the-box. If you use an earlier version of the Checkout API, you can make your integration compliant by adding additional front-end configuration.