Modern creative news

Subscription Export Process -

Jun 1, 2022

 STAKEHOLDERS

 Internal

  • The Payments/Product Team
  • CSM and Support

 External

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

 OVERVIEW

In the event that a customer is churning or wants to migrate the active subscriber of their existing one to an New Vendor, we have to export their subscription data which we store within our system. We then hand over the token for the New Vendor. The process typically takes about approximately 10 weeks.

 RELIABILITY

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 migrated to the new vendor, the Seller is the one responsible for subscription deactivation on the System so as to stop any unintentional billings or customers' complaints.

 Scope

  • Transferring active subscriber details to Seller.
  • Coordination with our current Payment Processor as well as the Seller's new Vendor to facilitate the migration of payment tokens.
  • Migration only for Credit Card tokens; due to compliance and regulations We are unable to migrate PayPal tokens.

 PROCEDURE

Subscription migration is a process that involves five stages:

  1. will provide active subscribers and list of subscribers, based upon processing type and payment method.
  2. will provide an official Letter of Intent (LOI) in the direction of the processor informing them of that the token is exported to the New Vendor. the LOI may differ between Processor to Processor.
  3. will connect the Seller, New Vendor, and current Payment Processor for token migration.

2.a. Current Processor will verify the AOC and any other PCI related data of the New Vendor.

2.b. Following PCI verification process, we will provide New Vendor with appropriate information regarding the next steps to be taken in the migration and timelines, which includes (but isn't limited to):

  • A specific protocol for processing that allows the transfer and reception of token files. It could also include the sharing of PGP keys (Public).
  • Schema for the file is expected by the vendor as well as the appropriate mapping ( will include the key or attribute for the tokens).
  • Processor specific steps to encrypt and decrypt information.
  1. Tokens will be transferred to the new Vendor through the Processor currently in place.
  2. Seller will deactivate the active subscription so that there are no double charges.

 PREREQUISITES

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

 Responsibilities

  1. :
  • Connect Sellers and New Vendors to Processors currently in use.
  • Send a Letter of Intent to every Processor.
  • Share details of the active subscribers, separated by Processor.
  • Rebill references can be shared that will serve as a identifier for mapping the tokens.
  1. Seller:
  • Provide New Vendor contact information and provide necessary compliance documents.
  • Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
  1. The Processor of the Present:
  • Contact New Vendor and confirming compliance with the requirements.
  • Accept Letter of Intent, and prepare for releasing tokens to New Vendor.
  • Coordinate with New Vendor for data transfer and also provide the schema for the New Vendor.
  1. New Vendor:
  • Connect with current Processor.
  • Provide all documents of compliance according to the requirements of the processor in the process.
  • Receive schema information from Processor as well as a rebill reference (Identifier) from .
  • Share sample data received from every Processor the intention of ensuring that data mapping is correct.

 RISKS

  • Data security: New Vendor and Seller have the responsibility for information security after it leaves the their system. Seller must ensure that the final customers' data is handled in a secure manner.
  • Rebills Seller is required to ensure their subscriptions are deactivated before they are debited again by the New Vendor, to avoid double re-bill.