# Fix failed TWINT payments from revoked mandates

When TWINT payments fail with the message "**The underlying mandate has been revoked by the buyer. Set up a new payment method and try again. Alternatively, the mandate may have been revoked by the issuer due to a collision with another created mandate**", the payment likely encountered a mandate collision.
## How to fix it
To fix this, make the connected account the merchant of record for all future TWINT recurring transactions, using one of the following:
- [Direct charges](docs.stripe.com/connect/direct-charges)
- [Destination charges](docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted#settlement-merchant) or [Separate charges and transfers](docs.stripe.com/connect/separate-charges-and-transfers?platform=web&ui=stripe-hosted#settlement-merchant)
  - With the `on_behalf_of` parameter set to the connected account ID
Here's an example of a [Setup Intents API](https://docs.stripe.com/api/setup_intents) request using the `on_behalf_of` parameter:
```
curl https://api.stripe.com/v1/setup_intents \
  -u sk_test_XXXXXXXXXXXXXXXXXXXXXXXX: \
  -X POST \
  -d amount=5000 \
  -d currency=chf \
  -d payment_method_types[]=twint \
  -d payment_method_data[type]=twint \
  --data-urlencode return_url="https://example-return.com" \
  -d confirm=true \
  -d usage=off_session \
  -d "customer={{CUSTOMER_ID}}"
  -d transfer_data[destination]=acct_CONNECTED123 \
  -d on_behalf_of=acct_CONNECTED123
```
## Why this happens
### How TWINT mandates work
TWINT is a payment method popular in Switzerland that enforces a one mandate per merchant-buyer pair scheme. If a new mandate is created between the same merchant and buyer, TWINT revokes the previous one. This can affect merchants using Connect.
### How a collision can happen
On a platform, a buyer can create mandates with multiple connected accounts. If each connected account is the merchant of record for its own mandates, there's no collision. But if the platform is merchant of record for both connected account mandates, TWINT revokes the first connected account's mandate. If the first connected account reauthorizes the mandate or creates a new one with the same buyer, TWINT revokes the second connected account's mandate.
## Reasons a mandate can be revoked
A mandate can be revoked for many reasons, including:
- **Single-active-mandate rule**
  - Some payment methods only allow a single active mandate per merchant–buyer pair. When a new mandate is created for the same buyer and merchant (or the same underlying account), the issuer or scheme may revoke the previous one.
- **Platform as merchant of record**
  - In some Connect use cases, the platform is the merchant of record for the payment method. If a connected account creates a new mandate, the issuer may treat it as replacing other active mandates owned by the platform and cancel them.
  - Examples include streaming or ridesharing platforms with connected accounts in multiple countries and a multinational platform as merchant of record. This can cause collisions for some local payment methods (LPMs).