The Thousand Solutions Blog

Subscriber Export Process

Jun 2, 2022

   STAKEHOLDERS  

   Internal  

  • Products Team and Payments
  • CSM and Support

External

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

   OVERVIEW  

If the customer's customer's churning has been taking place or they wish to transfer their current subscriber to New Vendor, we have to move their subscriber information to our database and hand over the token in directions of 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. If the information is passed to the seller it is the Seller who will be responsible for cancelling subscriptions in the System to ensure that there aren't from refunds due to error which could lead to the issue of customer complaints.

   Scope  

  • Transferring subscriber's active details to Seller.
  • Collaboration with our existing Pay Processor as well as the Vendor of Seller's new and innovative for payment token migration.
  • Transferring solely Credit Card tokens; due to the regulations and conformity, the company is unable to move PayPal tokens.

   PROCEDURE PROCEDURE FOR HTML1  

Subscriptions can be transferred using five steps:

  1. They will offer active subscribers as well as subscriber lists, depending on the payment processor and method of payment.
  2. The Processor is required to send an official Letter of Intent (LOI) upon request of the processor, which will identify the transfer of the token to the new Vendor. LOI differs from Processor to Processor in relation to Processor and Processor.
  3. Connect the Seller, new Vendor and current Payment Processor to facilitate token transfer.

2.a. Current Processors are required to confirm the AOC together with any other PCI relevant information for the New Vendor.

2.b. After PCI Verification Processor has been completed After PCI verification Processor is completed, we will provide the new vendor with appropriate details regarding the next steps to be followed during the migration procedure and the timeframes. This includes (but does not limit them to):

  • An exclusive protocol for the transfer and reception of token files. This could also involve sharing PGP keys (Public).
  • Schema of the documents that sellers should expect as well as the correct mapping ( should provide the key or attribute for tokens).
  • The specific processes used by processors to encode and decrypt information.
  1. Tokens will be distributed through the Vendor to be substituted by the Processor that is currently in operation.
  2. Seller will cancel the current subscription in order to make sure that there is no further charges.

   REQUIREMENTS  

  • New Vendor supports PCI compatible PCI in full.
  • If you are issued PAN numbers the additional security procedures as outlined by the processor must be taken.
  • The place where the subscription must be migrated.
  • The date for the migration is expected and last installment.

   Responsibilities  

  1. :
  • Connect new Vendors and Sellers using existing processes.
  • Offer a Letter of Intent to each processor.
  • The specifics of Shared Information for active subscribers. This information is broken down according to Processor.
  • Rebill references are shared , which is used as an identification for making the tokens available for mapping.
  1. Seller:
  • Contact new Vendor number as well as provide documentation to show the compliance.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. Current Processor:
  • Contact the New Vendor and confirming compliance to the standards required.
  • Request the Letter of Intent. Start to disperse tokens to New Vendor.
  • Work with a New Vendor for data transfer and provide the schema to the New Vendor.
  1. New Vendor:
  • Connect your processor.
  • Furnish all compliance documents as per the instructions of the processor throughout the process of.
  • Details about the schema are found from Processor as well as Rebill Reference (Identifier) from .
  • Share sample data received from each Processor with the intention to ensure that data mapping is completed.

   RISKS  

  • Security of data: The new Vendor as well as the Seller have the responsibility for secure data when it has left the system. Seller is responsible to ensure that the information of customers is treated in a secure way.
  • Rebills: Sellers are required to ensure that they can cancel their subscriptions be cancelled prior to getting charged by to the New Vendor, to avoid any double billing.

This article was originally posted this site

Article was first seen on here