Migrate from Sources-based Credit Transfers

Stripe’s EUR Bank Transfer product replaces the Sources-based SEPA Credit Transfer payment method, incorporating additional features and enhancements to improve functionality and payment capabilities. You can use it with Stripe PaymentIntents, Stripe Checkout, and Payment Element to streamline operations, reconciliation, and refunds.

Non-migration consequences

Stripe plans to disable support for local payment methods in the Sources API. If you currently handle any local payment methods using the Sources API, you must migrate them to the Payment Methods API. We’ll provide further information about this end of support through email notifications.

Impact on SEPA Credit Transfers customers

After migrating to Bank Transfers, Stripe will issue new bank account information for each of your existing users. You must communicate this change to your users to start sending funds to the new bank account. To ensure a smooth transition, we’ve added functionality to handle cases where your customer accidentally transfers funds into the existing SEPA Credit Transfer bank account by redirecting these funds into the EUR cash balance. This functionality will remain in place until March 2025. After that, we’ll begin to bounce any funds that land in these VBANs. Stripe won’t notify merchants about any bounced funds, as we’ll consider these accounts dormant and they’ll automatically reject any incoming funds.

Limitations for EUR Bank Transfers

Stripe allocates a new VBAN for customers after you migrate to Bank Transfers. As a result, VBAN limits will apply to your Bank Transfers integration. Learn more about VBAN limits.

During the migration process, only transfer customers who are actively making payments using bank transfers. For customers who aren’t actively using bank transfer as a payment method, Stripe performs a clean up of all Credit Transfer sources at a later date.

Differences between Credit Transfers and Bank Transfers

How Stripe migrates customer objects to support bank transfers

When you activate bank transfers, Stripe automatically enables your customer objects to support the cash balance, one of the main features of the bank transfers product.

• For a customer with no attached Credit Transfer Sources, Stripe provisions a new virtual account number for the cash balance.
• For a customer with attached Credit Transfer Sources, Stripe consumes the Credit Transfer Source object and moves the full remaining amount into the customer’s cash balance. See new transfers sent by the customer to the Source bank account number in the customer’s cash balance instead. The virtual account number changes during the migration process, and you will need to communicate the new destination to the customer.
• Single customers are automatically migrated after the following:
  • Request of Customer Balance Funding Instructions (recommended if you’re upgrading your integration)
  • Confirmation of a customer_balance Payment Intent
  • Creation of an invoice or subscription using bank transfers
  • For customers in testing environments, simulation of a funding transaction
• We guarantee that funds sent to the virtual account at any point in the future will be added to the correct customer cash balance.

Migrate Invoicing or Billing

If you’re using SEPA Credit Transfer payments with Invoicing or Billing and want to migrate, follow the steps in the Invoicing migration guide.

Migrate your direct integration with the Sources or Charges API

If you’re using SEPA Credit Transfers with the Sources API without Invoicing or Billing, follow the steps in the Sources migration guide.

Migrate your Connect integration

If your Connect platform integrates with Standard connected accounts using SEPA Credit Transfers, follow the steps in the Standard Connect integration guide.