PayPal Legacy (deprecated)
This page is retained for migration and troubleshooting guidance. Current V2 normally displays PayPal (Legacy) only if an account still has the old payment method saved as active, or only Legacy has been enabled in a controlled legacy environment.
Why PayPal Legacy may still be visible
The old setting technically consists of a PayPal email address and an activation switch. Deleting the saved email address also disables the Legacy payment method in V2. This technical feature for existing installations does not establish that a new merchant account should be connected in the same way.
If a Legacy entry is visible, check which published offers, outstanding bookings and old payment links still depend on it. Only change the process after fully testing the replacement solution.
Current replacement solutions
| Alternative | Suitable when | Configuration |
|---|---|---|
| PayPal Connect | You want to continue offering PayPal. | Connect onboarding and status checks instead of an email address. |
| Stripe | Cards and other methods approved by Stripe are required. | Stripe Connect and the current V3 integration. |
| Worldline / Saferpay | Your organisation has a suitable Worldline contract and terminal. | Customer ID, Terminal ID, API access and version 1.50. |
Switch without interrupting payments
Inventory offers where Legacy is still visible as a payment method.
Record outstanding legacy transactions, queries and refunds that are not yet complete.
Fully configure the replacement solution.
Test successful payment, cancellation, booking status, confirmation email and, if required, MustPay.
Enable the new payment method under Payment systems and check its selection in Design Manager and in the booking process for all affected offers.
Only disable Legacy and delete the old email setting once no active workflow still depends on it.
Handle outstanding legacy transactions
The current generic V2 refund feature is intended for Stripe, Worldline/Saferpay and PayPal V2, not PayPal Legacy. Resolve an old Legacy refund in the PayPal account used at the time, and record or document the financial correction in edoobox according to your invoicing process.
Keep the provider transaction ID, booking, amount, time and communication together. This makes it clear why a legacy case was not processed using the new PayPal Connect refund feature.
Check the existing connection before switching
Check the saved PayPal email address and document outstanding legacy payments. Configure the replacement connection and test the new payment route before disabling the old payment method. Switching does not turn an old transaction into a PayPal Connect transaction.
Example: Switch to PayPal Connect
An organisation wants to retain PayPal. It connects the business account through PayPal Connect, checks onboarding and a test payment, and only then replaces Legacy in all published offers. Outstanding old transactions remain documented separately.
Example: Switch from Legacy to Stripe
A course provider needs cards and SEPA in future. It configures Stripe V3, tests EUR and non-EUR offers and refunds, and then disables Legacy. MustPay is tested separately with an abandoned payment.
Example: An outstanding Legacy refund after migration
After the switch, someone contacts the team about an old payment. The team processes the refund in the PayPal account used at the time, records the provider ID and amount against the booking and creates the necessary invoice correction instead of sending the transaction through PayPal V2.
Check the current connection and payment purpose
Visibility of the old entry does not prove approval for a new process. After switching, check both the new PayPal Connect connection and the payment route actually visible in the published offer. The company card saved against the edoobox account is independent of both PayPal integrations.