Modern creative news

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 a customer churns, or decides to move their subscriber's active subscription to an New Vendor, we have to move their subscriber information which is saved in our system. We then transfer the token to the New Vendor. The procedure typically 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 to the Seller, the Seller is the one responsible for cancelling subscriptions via the System so as to avoid any accidental rebills and hence customers' complaints.

SCOP SCOP

  • Transferring active subscriber details to Seller.
  • We are working with our current payment Processor as well as the Seller's New Vendor to facilitate the transfer of payment tokens.
  • Only is only available for Credit Card tokens; due to regulations and compliance the business is not able to move PayPal tokens.

PROCEDURE

Subscription migration is a process that involves five steps:

  1. will provide active subscribers and subscription lists, based on the type of processing and payment process.
  2. They will issue an official Letter of Intent (LOI) in the direction of the processor which outlines the export of the token to the new Vendor. The LOI is different from Processor from Processor from Processor to Processor.
  3. Join the seller, the brand new Vendor and the current Payment Processor for easier token transfer.

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

2.b. In the aftermath of PCI validation We will then provide the New Vendor with appropriate information about the next steps that need to take in the process of migration, as well as timelines which comprises (but isn't restricted to):

  • Special transport protocols designed to processors that allow sending and receiving token file. Also, it could involve the sharing of PGP keystrokes (Public).
  • Schema for the data file is required by the vendor, as is the proper mapping ( will give the key/attribute for the tokens).
  • Processor specific steps to encrypt and decrypt the data.
  1. Tokens will be transferred into the Vendor's new account through the Processor currently in place.
  2. Seller will deactivate the subscription currently in place in order to prevent the possibility of double billing.

 REQUIREMENTS

  • The new Vendor's website has PCI fully PCI.
  • When receiving PAN numbers further security precautions as instructed by the Processor must be followed.
  • Store to which the subscription is required to be moved.
  • The date for the expected migration, and the date of the last bill.

Responsibilities

  1. :
  • Create connections for new vendors and sellers with current Processors.
  • Write a letter of intent to every Processor.
  • The details about shares of active subscribers. They are broken into segments by Processor.
  • Recall references are shared they serve as an reference to identify the tokens.
  1. Seller:
  • Get in touch with New Vendor contacts and furnish the necessary documents for compliance.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. The Processor of the Present:
  • Connect to New Vendor and confirming compliance with the requirements.
  • Get Letter of Intent. start to issue tokens. New Vendor.
  • Work With New Vendor for data transfer and provide schemas to New Vendor. New Vendor.
  1. New Vendor:
  • Connect to the current processor.
  • Provide all documents of compliance as asked by the current Processor.
  • Learn about schemas through Processor as well as Rebill Reference (Identifier) From .
  • Share sample data received from each processor to ensure appropriate data mapping.

 RISE

  • Data security: The new Vendor and Seller are responsible for all data security once it leaves system. Seller is the one responsible for making sure that customers' data is treated securely.
  • Rebills Seller must make sure that subscriptions can be cancelled prior to renewing through to the New Vendor, to avoid the double billing.

Article was posted on here