Moves a card payment source from one gateway account to another.
Use this operation to migrate payment methods between gateway accounts, such as when:
- consolidating gateway accounts
- switching from Spreedly to direct gateway integration
- aligning payment sources with regional/business unit gateway configurations
Supported gateways
See the Use Cases section for the list of supported source-destination gateway combinations.
Impact on reference_id
This operation updates the reference_id attribute of the payment source. In case you are using this value for any downstream system integrations, you will need to update the reference_id for the payment source in the downstream system to the new value.
Prerequisites & Constraints
- The
payment_source.typemust becard. - The destination payment gateway account must be active and not archived.
Impacts
- The following attributes are updated:
gateway_account_idgatewayreference_id- The role (primary or backup) of the payment source is not changed.
Use Cases
The API supports only the following source-destination gateway combinations:
| Source | Destination |
|---|---|
Any of the gateways via Spreedly. These include Authorize.net, Bambora, BlueSnap, Moneris, Orbital (Chase Paymentech), Paymill, PayPal Payments Pro, PayPal Payflow Pro, SagePay, Worldline Online Payments, Worldpay. |
|
| PayPal Express Checkout | PayPal Commerce |