STAKEHOLDERS

 Internal

• Payments/Product Team
• CSM and Support

 External

• Customer/Seller
• New Vendor
• Current Payment Processors(Cards only)

 OVERVIEW

When a client churns or wants to migrate the active subscriber of their existing one to a New Vendor, we have to export their subscription data that is stored in our system and hand over the token for the New Vendor. This usually takes around 10 weeks.

 PURPOSE

Migrating active subscriber/subscription data from the system and handing over the existing tokens via our existing Payment Processors to the New Vendor. After the data has been transferred, the Seller is accountable for the cancelling subscriptions in the System to avoid any stray refunds, and thus customers' complaints.

 SCOP

• Handing over active subscriber information to Seller.
• Coordination with our current Payment Processor as well as our Seller's New Vendor for payment token migration.
• Migration only for Credit Card tokens; due to regulations and compliance, we cannot migrate PayPal tokens.

 PROCEDURE

Subscription migration is a process that involves five stages:

1. will provide active subscribers and subscriber lists, based on payment method type and Processors.
2. will provide a signed Letter of Intent (LOI) for the processing company, informing them of the token export to the new vendor; The LOI will differ in Processor from Processor to Processor.
3. will connect the Seller, New Vendor with the existing Payment Processor for token migration.

2.a. Current Processor will verify the AOC as well as other PCI related information of the New Vendor.

2.b. Following PCI verification process, we will provide New Vendor with appropriate information on next steps in moving and the timeline, which include (but isn't limited to):

• Specific transport protocols for processors for sending and receiving token files. The process could also require exchanging PGP keys (Public).
• Schema of the file that is expected by the vendor as well as the appropriate mapping ( will provide the key/attribute for the tokens).
• Processor specific steps to encrypt and decrypt data.

1. Tokens will be transferred to the new vendor by the current Processor.
2. Seller is able to deactivate their active subscription on system so that there are no double charges.

 PREREQUISITES

• The New Vendor has been certified PCI compliant.
• When receiving PAN numbers the additional security procedures as required by the Processor must be observed.
• The Store where the subscription is required to be migrated.
• Expected date of migration and last charge.

 LIABILITY

1. :

• Connect Sellers and New Vendors to Processors currently in use.
• Send a Letter of Intent to each Processor.
• The share details of active subscribers, broken down by Processor.
• Rebill references can be shared which will act as a identifier for mapping the tokens.

1. Seller:

• Provide new Vendor contacts , and supply the appropriate documentation to demonstrate compliance.
• Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.

1. Current Processor:

• Connect with New Vendor and confirming compliance to the required requirements.
• Accept Letter of Intent, and prepare for releasing tokens New Vendor.
• Coordinate with New Vendor for data transfer and also provide the schema for the New Vendor.

1. New Vendor:

• Connect to the current processor.
• Complete all compliance documentation as asked by the Processor in charge.
• Get schema information from Processor as well as a rebill reference (Identifier) to .
• Send sample data to every Processor the intention of ensuring that data mapping is correct.

 RISKS

• Data security: New Vendor and Seller are responsible for all information security after it leaves the their system. Seller must ensure that the final customer's data is dealt with in a secure manner.
• Rebills Seller should ensure that subscriptions are deactivated before they are renewed by the New Vendor, to avoid double re-bill.