STAKEHOLDERS

 Internal

• Product Team and Payments
• CSM and Support

 External

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

 OVERVIEW

When a client churns or wants to migrate the active subscriber of their existing one to the New Vendor, we have to transfer their subscription information which is saved within our system. We then hand over the token for the New Vendor. The process typically takes about approximately 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 to the new vendor, the Seller is responsible for subscription deactivation on the System so as to stop any unintentional billings or customers' complaints.

 SCOP

• Transmitting active subscriber data to Seller.
• Coordination with our current Payment Processor and the Seller's New Vendor for payment token migration.
• We are only transferring Credit Card tokens; due to regulations and compliance the company is unable to transfer PayPal tokens.

 PROCEDURE

Subscription migration is a process that involves five actions:

1. We will give active subscribers and subscriber lists, based on payment method type and Processors.
2. will provide an official Letter of Intent (LOI) for the processing company, indicating the export of the token to the New Vendor; The LOI will differ between Processor the Processor.
3. will connect the Seller, new Vendor with the existing Payment Processor to facilitate token transfer.

2.a. Current Processor will verify the AOC and any other PCI relevant information for the New Vendor.

2.b. After PCI verification Processor is completed, we will provide New Vendor with appropriate information on next steps in migration and timelines, which includes (but is not limited to):

• Processor specific transport protocol to send and receive token files. It could also include the sharing of PGP keys (Public).
• Schema of the file that is expected by the vendor and appropriate mapping ( will include the key or attribute to the tokens).
• The processor has specific steps for encrypting and decrypt the information.

1. Tokens will be given to the New Vendor by the Processor currently in place.
2. Seller will deactivate the active subscription on system to avoid double charges.

 PREREQUISITES

• New Vendor's website is PCI certified.
• If receiving PAN numbers, further security measures as directed by the Processor must be followed.
• Store to which the subscription must be transferred.
• Expected date of migration and last charge.

 Responsibilities

1. :

• Connect new Vendors and Sellers to current Processors.
• Offer a Letter of Intent for each Processor.
• Details of Shared Information for active subscribers, broken down by Processor.
• Rebill references are shared, it will be used as an identifier to map the tokens.

1. Seller:

• Provide the latest Vendor contacts and furnish necessary compliance documents.
• 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 with the requirements.
• Accept Letter of Intent, and begin to release tokens to New Vendor.
• Coordinate with New Vendor for data transfer and supply schemas to the New Vendor.

1. New Vendor:

• Connect with current Processor.
• Furnish all compliance documents in accordance with the request of the Processor in charge.
• Get schema information from Processor as well as a rebill reference (Identifier) From .
• Distribute sample data from every Processor in order to make sure that the data is properly mapped.

 RISE

• Data security: Both the new Vendor and Seller are responsible for all information security after it leaves the their system. Seller should ensure that end customers' information is treated using appropriate security.
• Rebills Seller must ensure subscriptions have been cancelled prior to being renewed through the New Vendor, to avoid the double bill.