Creative Hosting News

Subscriber Export Process

Jun 2, 2022

 STAKEHOLDERS

Internal

  • Products Team and Payments
  • CSM and Support

External

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

OVERVIEW

If customers are churning out or is looking to transfer the active subscriber of their existing one to an New Vendor, we have the capacity to obtain their subscriber details, which we store in our database. We then transfer the token to the New Vendor. This usually takes around up about 10 to 14 weeks.

PURPOSES

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 transferred and the data is transferred, the Seller is responsible for subscription deactivation on the System to avoid any stray billings or customers' complaints.

 SCOP

  • Transmitting active subscriber data for Seller.
  • Coordinating with our existing Payment Processor along with our Seller's new Vendor to facilitate the migration of payment tokens.
  • Migrating only Credit Card tokens; due the compliance requirements and rules this company cannot transfer PayPal tokens.

HTML1 PROCEDURE PROCEDURE

Subscription migration involves five steps:

  1. They will offer active subscribers as well as the list of subscribers according to the type of payment method and processors.
  2. Processors will give the processor the processor with a certified Letter of Intent (LOI) to the processing company, indicating the transfer of the token for the New Vendor. LOI varies in Processing to Processor.
  3. The Seller can be connected to the the brand new Vendor and the current payment processors to allow the movement of tokens.

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

2.b. After PCI verification Processor's process has been completed We will be able to provide the new Vendor with appropriate information about the next steps in moving along with the timeframe comprising (but doesn't limit itself to):

  • An exclusive protocol to transfer and receive token files. It could also be necessary to share PGP keys (Public).
  • Schema for the file vendors should anticipate as well as the appropriate mapping ( includes the key or attribute for these tokens).
  • Specific steps taken by the processor in order to encode and decode the data.
  1. Tokens will be transferred to the new Vendor via the existing Processor.
  2. Seller will deactivate the active subscription to avoid the double charge.

 REQUIREMENTS

  • New Vendor's website has been PCI certified.
  • In the event of receiving PAN numbers, then additional security measures , as instructed by the Processor must be followed.
  • Store from which subscription is to be transferred.
  • The date of the expected migration as well as the last payment.

LIABILITY LIABILITY

  1. :
  • Create connections for new Sellers and Vendors with current Processors.
  • Write a letter of intent to each Processor.
  • Share details for active subscribers are separated out by Processor.
  • Rebill references are shared, to serve as an identifier for mapping the tokens.
  1. Seller:
  • Give new Vendor contacts , and supply all the necessary documentation to prove conformity.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. This is the Processor that allows for the Present:
  • Get in touch with New Vendor and confirming compliance requirements.
  • Get the Letter of Intent. Then, begin to release tokens to New Vendor.
  • Collaborate with New Vendor for data transfer and supply schema to the New Vendor.
  1. New Vendor:
  • Connect to the current processor.
  • Completion of all documentation for compliance according to the requirements of the present Processor.
  • Find the schema details from Processor along with a rebill Reference (Identifier) for .
  • Distribute sample data from each processor to ensure appropriate data mapping.

Risques

  • Security of data Security of data Vendor as well as the Seller are accountable for protection of the data after it leaves the system; Seller must ensure that the final customer's personal data are handled with the appropriate level of security.
  • Rebills: Seller must ensure subscriptions have been terminated prior to being billed again from the New Vendor, to avoid double re-bill.

Article was first seen on here