STAKEHOLDERS

 Internal

• The Payments/Product Team
• CSM and Support

 External

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

 OVERVIEW

When a client churns or decides to move their current subscriber to an New Vendor, we have to transfer their subscription information which we store in our system and give the token over to the New Vendor. This usually takes around 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. Once the data is migrated and the data is transferred, the Seller is responsible for subscription deactivation on the System so as to stop any unintentional billings or customers' complaints.

 Scope

• Handing over active subscriber information to Seller.
• Coordination with our current Payment Processor and the Seller's New Vendor to facilitate the migration of payment tokens.
• Migration only for Credit Card tokens; due the compliance requirements and rules 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 processing type and payment method.
2. will provide the processor with a signed Letter of Interest (LOI) in the direction of the processor indicating the token export to the New Vendor; LOI varies in Processor to Processor.
3. Connect the Seller, new Vendor, and current payment processor to enable token movement.

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

2.b. Once PCI verification Processor has been completed We will then provide the New Vendor with appropriate information about the next steps of moving and the timeline, which includes (but does not limit itself to):

• Processor specific transport protocol that allows the transfer and reception of token files. This step might also involve the sharing of PGP keys (Public).
• Schema for the file the vendor should expect and the proper mapping ( will provide the key/attribute for tokens).
• The processor has specific steps for encrypting and decrypt data.

1. Tokens will be given to the new vendor by the current Processor.
2. Seller will remove the active subscription on system to avoid double charges.

 PREREQUISITES

• The New Vendor has been certified PCI fully PCI.
• In the event of receiving PAN numbers additional security steps as mandated by the Processor needs to be followed.
• Store to which the subscription needs to be migrated.
• Expected date of migration and last charge.

 LIABILITY

1. :

• Connect Sellers and New Vendors to current Processors.
• Provide Letter of Intent to each processor.
• The share details of active subscribers, broken down by Processor.
• Rebill references can be shared that will serve as an identifier that maps the tokens.

1. Seller:

• Give the latest Vendor contacts , and supply appropriate compliance documentation.
• 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.
• Get the Letter of Intent. Then begin to release tokens for New Vendor.
• Co-ordinate With New Vendor for data transfer and provide schema for that New Vendor.

1. New Vendor:

• Connect to your current processor.
• Provide all documents of compliance in accordance with the request of the Processor in charge.
• Receive schema information from Processor and Rebill Reference (Identifier) from .
• Share sample data received from every Processor in order to make sure that the data is properly mapped.

 RISE

• Security of data: The new Vendor and Seller are responsible for all information security after it leaves the their system. Seller should ensure that end customer's data is dealt with in a secure manner.
• Rebills Seller must ensure subscriptions can be cancelled before being renewed through the New Vendor, to avoid the double bill.