STAKEHOLDERS

 Internal

• Payments/Product Team
• CSM and Support

 External

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

 OVERVIEW

In the event that a customer is churning or wishes to transfer their current subscriber to the New Vendor, we have the ability to extract their subscription details which is saved in our system and give the token over to the New Vendor. The process typically takes about up to 10 weeks.

 RELIABILITY

Migrating active subscriber/subscription data from the system and handing over the existing tokens via our existing Payment Processors to the New Vendor. When the data has been migrated, the Seller is accountable for the cancellation of subscriptions on the System in order to prevent any accidental billings or customer complaints.

 Scope

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

 PROCEDURE

Subscription migration involves the following five stages:

1. We will give active subscribers and subscriber lists, based on the type of payment method and processors.
2. They will issue the processor with a signed Letter of Interest (LOI) for the processing company, indicating the export of the token to the New Vendor; The LOI will differ from Processor the Processor.
3. Connect the Seller, New Vendor, and current Payment Processor for token migration.

2.a. Current Processor will verify the AOC and other PCI related data of the New Vendor.

2.b. Once PCI verification Processor has been completed, we will provide New Vendor with appropriate information on next steps in transition and timeframes. This includes (but does not limit itself to):

• Specific transport protocols for processors that allows the transfer and reception of token files. The process could also require the sharing of PGP keys (Public).
• Schema for the file the vendor should expect and appropriate mapping ( should provide the key/attribute for tokens).
• Specific steps taken by the processor to encode and decrypt the information.

1. Tokens will be handed over to the new vendor by the current Processor.
2. Seller is able to deactivate their active subscription on system in order to prevent double billing.

 PREREQUISITES

• New Vendor's website is PCI fully PCI.
• When receiving PAN numbers additional security steps as mandated by the Processor must be followed.
• The Store where the subscription is required to be moved.
• Expected date of migration and the last payment.

 Responsibilities

1. :

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

1. Seller:

• Give 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 to New Vendor and confirming compliance with the requirements.
• Accept Letter of Intent, and prepare for releasing tokens New Vendor.
• Coordinate the New Vendor for data transfer and also provide the schema for New Vendor. New Vendor.

1. New Vendor:

• Connect with current Processor.
• Complete all compliance documentation as asked by the processor in the process.
• Get schema information from Processor and rebill reference (Identifier) to .
• Distribute sample data from each processor the intention of ensuring that data mapping is correct.

 RISKS

• Security of data: The new Vendor and Seller are accountable for data security once it leaves system. Seller should ensure that end customers' data is handled using appropriate security.
• Rebills: Seller must ensure subscriptions are deactivated before they are renewed from the New Vendor, to avoid double re-bill.