Strong Customer Authentication for destination charges created by a non-European Economic Area platform for EEA-based connected accounts with EEA-based customers
If your platform uses destination charges and is is not in the European Economic Area (EEA), but your connected account(s) and their end customers are in the EEA, the charge may be subject to Strong Customer Authentication. This depends on the Merchant Of Record and if the on_behalf_of header is used. If this header is not used, then the transaction is considered one-leg and is outside the scope of Strong Customer Authentication (SCA).
Example
This table covers scenarios where the Platform location is non-EEA, while the connected account and the cardholder are both in the EEA.
Charge type |
Merchant of record |
SCA required |
Connected account |
Yes |
|
Platform |
No |
|
Connected account |
Yes |
|
Platform |
No |
More info
- Using on_behalf_of
- API reference for on_behalf_of
- Creating Charges and Taking Fees: Stripe Connect
Did this answer your question?
Related articles