Creative news fork

Subscriber Export Process -

Jun 2, 2022

 STAKEHOLDERS

 Internal

  • The Payments/Product Team
  • CSM and Support

External

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

Overview

If customers are churning, or is looking to transfer an active subscriber from their current one to a New Vendor, we have to export their subscription data stored in our system. We then hand over their token to an New Vendor. The process typically takes about roughly 10 weeks.

RELIABILITY RELATABILITY

Migrating active subscriber/subscription data from the system and handing over the existing tokens via our existing Payment Processors to the New Vendor. After the data has been transferred over to the brand new provider the Seller is accountable for deactivating subscriptions in the System in order to prevent the unintentional charging of customers or complains.

 Scope

  • Transferring subscriber's active details to Seller.
  • Collaboration with our present Pay Processor as well as the new Seller's Vendor to facilitate the migration of payment tokens.
  • Only to Credit Card tokens; due to the compliance requirements and rules we cannot move PayPal tokens.

 PROCEDURE

Subscription migration is a procedure that has five steps:

  1. will provide active subscribers and lists of subscribers, based upon processing type and payment technique.
  2. will provide an formal letter of intent (LOI) in directions to the processor, informing that the token has been transferred into the New Vendor. the LOI could differ from Processor to Processor.
  3. The Seller will be connected to the new Vendor as well as the current payment processor to enable token movement.

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

2.b. In the aftermath of the PCI Verification process After PCI verification, we will provide New Vendor with appropriate information concerning the next steps to be followed during the migration and timelines including (but not limited to):

  • An exclusive protocol which allows for the transfer and reception of token files. This could include exchange with PGP keys (Public).
  • Schema of the file will be expected from the vendor, and the proper mapping ( includes the key or attribute that corresponds to those tokens).
  • The processor has specific steps for encrypting and decrypt data.
  1. Tokens will be transferred the new Vendor via the Processor that is currently in operation.
  2. Seller will cancel the current subscription, ensuring that there is no additional charges.

PREREQUISITES

  • New Vendor supports PCI and fully PCI.
  • When receiving PAN numbers additional security steps as mandated by the Processor needs to be completed.
  • The store where the subscription must be transferred.
  • The date for migration is expected to be the day of the date of last billing.

Responsibilities

  1. :
  • Connect New Vendors and Sellers with Processors in operation.
  • Write a letter of intent to every Processor.
  • Details of active subscribers, separated by Processor.
  • Rebill references can be shared that will serve as a unique identifier when mapping the tokens.
  1. Seller:
  • Provide New Vendor contact details and supply necessary compliance documents.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. A Processor for the Present:
  • Make contact with the New Vendor and confirming compliance with the regulations.
  • Accept Letter of Intent and prepare for releasing tokens to New Vendor.
  • Coordinate the New Vendor for data transfer as well as providing an appropriate schema for New Vendor.
  1. New Vendor:
  • Connect with the processor currently in use.
  • Provide all documents of compliance as per the needs of the processor during the course of the processing.
  • Receive schema information from Processor and also Rebill number (Identifier) From .
  • Share sample data received from every Processor the intention of ensuring that data mapping is correct.

RISKS

  • Security of data: Both the Vendor and Seller are responsible for information security after it has left their system. Seller must ensure that the final customers' data is handled in a secure manner.
  • Rebills Seller is required to make sure that their subscriptions are cancelled prior to being debited again through the New Vendor, to avoid double re-bill.

Article was first seen on here