Creative news

Subscriber Export Process -

Jun 2, 2022

   STAKEHOLDERS  

   Internal  

  • The Payments/Product Team
  • CSM and Support

   External  

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

   Overview  

If an existing customer switches to churning or decides to switch their current subscriber to a different Vendor We must move their subscriber information which we store in our system and give the authorization onto the New Vendor. This usually takes around 10 weeks.

   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, the data is transferred, after the data has been transferred to the seller, the vendor is accountable for the subscription deactivation in the System in order to prevent the unintentional charging or customer complains.

   Scope  

  • Handing over active subscriber information to Seller.
  • Coordinate with our present payment Processor and Seller's new Vendor for a smoother exchange of tokens for payment.
  • The only exception is to use Credit Card tokens; due the compliance rules and compliance, the business cannot perform transactions with PayPal tokens.

   PROCEDURE  

Subscription migration is an action which involves five steps:

  1. We will provide subscribers who are active , and lists of subscriber names according to the kind of processing and payment method.
  2. The processor will send the processor with a signed Letter of Intent (LOI) to the instructions of the processor, indicating that the export of the token is to the New Vendor the LOI may vary in Processor to Processor.
  3. Sign up to the seller, the brand new Vendor as well as the current payment processor to enable token movement.

2.a. Current Processor is required to verify the AOC together with the any other PCI relevant data from the New Vendor.

2.b. Once the PCI validation process has been completed after which we will notify the new vendor appropriate details regarding the next steps and the timeline that comprises (but isn't limited to):

  • A specific protocol for the processor , which allows for the exchange and reception of tokens. It could also involve sharing PGP keys (Public).
  • Schema for the format the vendor will be expecting and the correct mapping ( should include the key or attribute for tokens).
  • The processor is equipped with methods to decrypt and encode information.
  1. The tokens will be distributed to the new seller by the Processor.
  2. Seller is going to remove the current subscription in the system to prevent the double cost.

   HTML1 Requirements  

  • The New Vendor has been certified PCI completely PCI.
  • In the event of receiving PAN numbers, additional security procedures that are required by the Processor have to be taken.
  • The Store to where the subscription has to be transferred.
  • The date of migration is likely to fall on the day of the date of the billing.

   LIABILITY LIABILITY  

  1. :
  • Connect Sellers and New Vendors to the Processors that are currently used.
  • Offer a Letter of Intent for each processor.
  • Information about the shares of active subscribers, broken into segments according to Processor.
  • The Rebill reference is able to be shared to act as an identifier that is used to map tokens.
  1. Seller:
  • Provide the most current Vendor contact information, and also the appropriate documents to prove compliance.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. The Processor of the Present:
  • Make contact with New Vendor and confirming compliance with the requirements.
  • Ask for the letter of intention. Then begin to release tokens to support the New Vendor.
  • Work with New Vendor for data transfer and provide schema for that New Vendor.
  1. New Vendor:
  • Connect to your processor.
  • Documents of compliance are required to the requirements of the processor in charge.
  • Get schema details from Processor In addition, get Rebill Reference (Identifier) from .
  • Share sample data with each Processor to be sure that the data is correctly and appropriately mapped.

   RISE  

  • Data security Vendor and Seller are responsible for data security once it has left the data system. Seller should ensure that end data of customers is secure.
  • Rebills Seller must ensure that the subscription is cancelled prior to renewal by informing the New Vendor, to avoid having to pay a double bill.

The article was published on this site

This post was first seen on here