Export of Subscribers -

Jun 2, 2022

 STAKEHOLDERS

 Internal

  • Product Team and Payments
  • CSM and Support

 External

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

A OVERVIEW

If a customer churns or decides to switch their current subscriber to the New Vendor, we have to export their subscription data which we store within our system. We then move the token to new customers to the New Vendor. The process typically takes between to 10 weeks.

TRUSTABILITY

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 to the new vendor, the Seller is the one responsible for cancellation of subscriptions on the System in order to prevent the possibility of refunds that are not intended as well as the risk of customer complaints.

 Scope

  • Transferring active subscriber details to Seller.
  • Collaboration with our existing Pay Processor as well as the Seller's brand new Vendor to ease the transfer of payment tokens.
  • Only transferring Credit Card tokens; due to the regulations and conformity the company is unable to change PayPal tokens.

 PROCEDURE

The migration of subscriptions involves five phases:

  1. We'll give active subscribers and subscriber lists, based on payment method type and Processors.
  2. The Processor will notify the processor the signed Letter of Interest (LOI) that is in directions of the processor to indicate that the token is exported to the new vendor. The LOI will differ in Processor that of the Processor.
  3. will connect the Seller, new Vendor and the existing payment processors to allow the movement of tokens.

2.a. 2.a. The Current Processor will confirm the AOC along with any additional PCI relevant information provided by the New Vendor.

2.b. After the PCI verification process We will follow up with to the New Vendor with appropriate information about the next steps that need to be followed during the transition and the timeline, that includes (but not restricted to):

  • Special protocols of transport for processors to transfer and receive token files. The process could also require that keystrokes be shared. PGP keystrokes (Public).
  • Schema of the document is expected by the vendor and the proper mapping ( will include the key or attribute for these tokens).
  • Processor specific steps to encrypt and decrypt the information.
  1. The tokens will be assigned to the New Vendor by the current Processor.
  2. Seller can deactivate their active subscription on system in order to prevent double billing.

 PREREQUISITES

  • New Vendor supports PCI and fully PCI.
  • In the event of receiving PAN numbers the additional security measures demanded by the Processor have to be adhered to.
  • The Store where the subscription is required to be transferred.
  • When the migration is expected to occur and the final payment.

Responsibilities

  1. :
  • Link new Sellers and Vendors to the Processors that are currently being used.
  • Send a Letter of Intent to every Processor.
  • Details of Shared Information for current subscribers separated by Processor.
  • Rebill references are shared, which will act as a identification number for the tokens to be mapped.
  1. Seller:
  • Make the latest Vendor contact details and provide documents to show compliance.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. A Processor for the Present:
  • Connect with New Vendor and confirming compliance with the requirements.
  • Accept the Letter of Intent and then prepare to release tokens for New Vendor.
  • Co-ordinate the new Vendor for data transfer and also provide the schema for that New Vendor.
  1. New Vendor:
  • Connect to the processor currently in use.
  • Complete all compliance documentation in accordance with the request of the processor in the process.
  • Information about the schema from Processor and forward a reference to rebill (Identifier) from .
  • Send sample data to every Processor to be sure the data is properly mapped.

Risques

  • Security of data Data security: Both the new Vendor as well as the Seller are accountable for information security after it leaves the system. Seller is responsible for making sure that the information of customers is handled with appropriate security.
  • Rebills Seller is required to make sure that their subscriptions are not activated before they are renewed with the New Vendor, to avoid the double bill.

Article was posted on here