nftified news

Subscriber Export Process

Jun 1, 2022

 STAKEHOLDERS

 Internal

  • The Payments/Product Team
  • CSM and Support

 External

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

A OVERVIEW

If a client churns or decides to move the active subscriber of their previous account to their New Vendor, we have to transfer their subscription information that is stored within our system. We then transfer the subscription token to that direction to the New Vendor. This process usually takes around 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 is transferred over to the brand new provider, the Seller is the one accountable for deactivating subscriptions on the System so as to avoid any unintentional refunds which could lead to customers complaining.

SCOP

  • Sending active subscriber details for Seller.
  • Coordinating with our current Payment Processor and Seller's new Vendor to facilitate payments tokens transfer.
  • Migrating only Credit Card tokens; due the strict compliance rules and requirements this company cannot move PayPal tokens.

PROCESS

Subscription migration is a process with five stages:

  1. We'll provide active subscribers and subscriber lists, based on the processing type and the payment process.
  2. They will issue an official Letter of Intent (LOI) for the processing company, indicating the transfer of the token to the New Vendor; The LOI is different for each Processor processor.
  3. The Seller will be connected to the new Vendor and the existing payment processor to facilitate the movement of tokens.

2.a. The current Processor will confirm the AOC along with any additional PCI pertinent data for the New Vendor.

2.b. Once the PCI validation process has been completed After PCI verification process is completed, we will provide New Vendor with appropriate information concerning the next steps to migration and timelines, which includes (but doesn't have to be restricted to):

  • Specific transport protocols for processors for sending and receiving token files. This could include sharing PGP keystrokes (Public).
  • Schema of the documents that vendors should be expecting and the proper mapping ( will provide the key/attribute of these tokens).
  • Specific steps taken by the processor for the purpose of encoding and decrypt information.
  1. Tokens will be given to the new vendor by the current Processor.
  2. Seller will deactivate the active subscription to the system to prevent duplicate payment.

 REQUIREMENTS

  • New Vendor has been PCI accredited.
  • If you receive PAN numbers, additional security measures as mandated by the Processor should be taken.
  • Store from which subscription is to be transferred.
  • The time for the migration date is likely to fall on the day of the date of the last bill.

 Requirements

  1. :
  • Link new Sellers and Vendors with current Processors.
  • A Letter of Intent should be sent to every Processor.
  • Specifics of Shared Information to active subscribers. Separated from the Processor.
  • Share the rebill reference, that will serve as a identifier for mapping the tokens.
  1. Seller:
  • Get in touch with the any new Vendor contacts and furnish necessary compliance documents.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. The Processor of the Present:
  • Connect with New Vendor and confirming compliance to the required requirements.
  • Receive the letter of intent. Then begin to release tokens in support of New Vendor.
  • Use with the New Vendor for data transfer and also provide the schema to the New Vendor.
  1. New Vendor:
  • Connect to the current processor.
  • All documents must be submitted according to the requirements of the current Processor.
  • Learn about schemas from Processor and rebill reference (Identifier) From .
  • Make sure to send samples of data to every processor in order to make sure that the data is mapping.

 Risks

  • Data security: Both the new Vendor as well as the Seller are responsible for the secure data when it has left the systems they have in place. Seller must ensure that final customers' information is protected with adequate security.
  • Rebills Sellers should make sure subscriptions are removed before being billed again by to the New Vendor, to avoid double re-billing.

Article was posted on here