Creative news

Subscriber Export Process

Jun 2, 2022

   STAKEHOLDERS  

   Internal  

  • The Product and Payments Team
  • CSM and Support

   External  

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

   An OVERVIEW  

When a customer churns, or decides to move the active subscriber of their previous accounts to the New Vendor, we have to move their subscriber information stored in our system. We then transfer the subscription token to that direction into the New Vendor. This usually takes approximately 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. Once the information is handed over to the brand new service provider, the Seller is accountable for deactivating subscriptions within the System so as to avoid accidental refunds that may cause customers to complain.

   SCOP  

  • Sending active subscriber details for Seller.
  • Working with our current Payment Processor and Seller's new Vendor for the purpose of facilitating payments token transfer.
  • Only transferring Credit Card tokens; due the strict rules of compliance and regulations the company is unable to move PayPal tokens.

   PROCESS  

Subscription migration is a procedure comprising five steps:

  1. We'll give active subscribers as well as subscriber lists, depending on the type of processing used and the payment process.
  2. They'll issue a formal Notice of Intent (LOI) to the processing company, indicating how the token will be transferred to the New Vendor; The LOI is different for each Processor processor.
  3. The Seller will connect to the new Vendor and the existing payment processor in order to ease the transfer of tokens.

2.a. The present Processor will verify the AOC together with any other PCI pertinent data for that New Vendor.

2.b. After the PCI validation process is successfully completed, after the PCI verification process is done, we'll provide the New Vendor with appropriate information regarding the next steps in migration and timelines, which comprises (but doesn't have to be only):

  • Special transport protocols are used by processors that allow for the transfer and reception of token files. It could also include sharing PGP keystrokes (Public).
  • Schema of documents vendors should be expecting and the appropriate mapping ( will give the key/attribute for these tokens).
  • Particular steps are performed by the processor for purposes of decoding and decrypting data.
  1. Tokens will be given to the new vendor through the existing Processor.
  2. Seller will deactivate the active subscription in the system to avoid duplicate payments.

   REQUIREMENTS  

  • New Vendor has been PCI accredited.
  • If you have received PAN numbers, additional security measures required by the Processor need to be taken.
  • The Store where subscriptions are to be transferred.
  • The migration will likely fall on the day of the day of the previous bill.

   Requirements  

  1. :
  • Link new Sellers and Vendors to Processors currently in use.
  • The Letter of Intent must be sent out to each processor.
  • Specifics of Shared information to subscribers who are active. Separated from the processor.
  • Rebill references can be shared which will act as an identification number for the tokens to be mapped.
  1. Seller:
  • Contact anyone who has been added to the Vendor contacts and supply the required conformity documents.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. A Processor for the Present:
  • Contact the New Vendor and confirming compliance to the necessary requirements.
  • Accept the letter of intent. After that, begin to distribute tokens to support the New Vendor.
  • Use with the New Vendor to transfer data and to also supply the schema to that New Vendor.
  1. New Vendor:
  • Connect to the current processor.
  • The documents submitted must conform in accordance with the specifications of the Processor in force.
  • Find out about schemas by Processor and rebill reference (Identifier) From .
  • Be sure to provide the data samples to each processor so that you can be sure the data has been being mapped.

   Risques  

  • Security of the data. Both the new Vendor and the Seller are accountable for secure data when it is no longer in the systems they have in place. The Seller is responsible for ensuring that the final customer's information is secured by ensuring adequate security.
  • Rebills Sellers need to ensure they have removed their subscriptions prior to they are re-billed by the New Vendor, to avoid duplicate re-billing.

The article was published on here

Article was first seen on here