STAKEHOLDERS

 Internal

• Product Team and Payments
• CSM and Support

 External

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

 OVERVIEW

If a customer churns, or decides to move their active subscriber from to a New Vendor, we have to transfer their subscription information which is saved in our system and hand over the token to the New Vendor. This process usually takes approximately 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 the one responsible for cancellation of subscriptions on the System in order to prevent any accidental rebills and hence customer complaints.

 SCOP

• Handing over active subscriber information to Seller.
• Working 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 to regulations and compliance the company is unable to transfer PayPal tokens.

 PROCEDURE

Subscription migration is a process that involves five steps:

1. will provide active subscribers and subscription lists, based on processing type and payment method.
2. will provide an official Letter of Intent (LOI) to the processor, indicating the token export to the New Vendor; The LOI will differ between Processor from Processor to Processor.
3. Connect the Seller, new Vendor as well as the current Payment Processor to facilitate token transfer.

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

2.b. Following PCI verification process, we will provide New Vendor with appropriate information regarding the next steps to be taken in the migration and timelines, which comprises (but isn't limited to):

• Specific transport protocols for processors for sending and receiving token files. It could also include sharing PGP keystrokes (Public).
• Schema for the file is expected by the vendor and the proper mapping ( will provide the key/attribute for the tokens).
• Processor specific steps to encrypt and decrypt data.

1. Tokens will be handed over to the new Vendor through the current Processor.
2. Seller will deactivate the current subscription in order in order to prevent double billing.

 PREREQUISITES

• New Vendor's website is PCI fully PCI.
• When receiving PAN numbers further security measures as directed by the Processor needs to be observed.
• Store to which the subscription needs to be migrated.
• Expected date of migration and the date of last billing.

 Responsibilities

1. :

• Connect New Vendors and Sellers with current Processors.
• Send a Letter of Intent to every Processor.
• The share details of active subscribers, broken down by Processor.
• Rebill references are shared, which will act as a identifier for mapping the tokens.

1. Seller:

• Contact New 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 to New Vendor and confirming compliance requirements.
• Receive Letter of Intent and begin to release tokens New Vendor.
• Work With New Vendor for data transfer and supply schemas to New Vendor. New Vendor.

1. New Vendor:

• Connect with current Processor.
• Provide all documents of compliance as asked by the current Processor.
• Get schema information from Processor and Rebill Reference (Identifier) From .
• Share sample data received from each processor to ensure appropriate data mapping.

 RISE

• Data security: New Vendor and Seller are responsible for all data security once it leaves system. Seller is responsible for ensuring that customers' data is handled in a secure manner.
• Rebills Seller must ensure subscriptions can be cancelled before being renewed through the New Vendor, to avoid double re-bill.