Subscription Export Process -
STAKEHOLDERS
Internal
- The Payments/Product Team
- CSM and Support
External
- Customer/Seller
- New Vendor
- Current Payment Processors(Cards only)
OVERVIEW
If a customer churns, or decides to move the active subscriber of their existing one to a New Vendor, we have to transfer their subscription information which is saved in our database and then give the token over to the New Vendor. The process typically takes about up to 10 weeks.
PURPOSE
Migrating active subscriber/subscription data from the system and handing over the existing tokens via our existing Payment Processors to the New Vendor. When the data has been migrated to the new vendor, the Seller is responsible for cancellation of subscriptions on the System so as to stop any unintentional refunds, and thus customers' complaints.
SCOPE
- Handing over active subscriber information to Seller.
- Working with our current payment Processor as well as the Seller's new Vendor for the transfer of payment tokens.
- We are only transferring Credit Card tokens; due to compliance and regulations the company is unable to transfer PayPal tokens.
PROCEDURE
The migration of subscriptions involves five stages:
- will provide active subscribers and subscriber lists, based on the type of payment method and processors.
- will provide a signed Letter of Intent (LOI) for the processing company, which identifies the export of the token to the new vendor; The LOI will differ from Processor from Processor to Processor.
- Connect the Seller, new Vendor, and current Payment Processor to facilitate token transfer.
2.a. Current Processor will verify the AOC as well as other PCI relevant information for the New Vendor.
2.b. After PCI verification Processor We will then provide the New Vendor with appropriate information about the next steps of migration and timelines, which includes (but isn't limited to):
- Processor specific transport protocol to send and receive token files. This step might also involve sharing PGP keystrokes (Public).
- Schema of the document that the vendor should expect and appropriate mapping ( should provide the key/attribute for the tokens).
- Specific steps taken by the processor to encode and decrypt information.
- Tokens will be handed over to the new Vendor through the current Processor.
- Seller will remove the active subscription so that there are no double charges.
PREREQUISITES
- New Vendor is PCI fully PCI.
- In the event of receiving PAN numbers additional security steps as mandated by the Processor must be taken.
- The Store where the subscription must be migrated.
- Date of expected migration and last charge.
Responsibilities
- :
- Connect Sellers and New Vendors to current Processors.
- Provide Letter of Intent to every processor.
- Details of Shared Information for current subscribers, broken down by Processor.
- Rebill references can be shared which will act as an identifier to map the tokens.
- Seller:
- Give the latest Vendor contact information and provide appropriate compliance documentation.
- Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
- Current Processor:
- Connect with New Vendor and confirming compliance with the requirements.
- Get the Letter of Intent. Then prepare for releasing tokens New Vendor.
- Work with New Vendor for data transfer and supply schemas for the New Vendor.
- New Vendor:
- Connect to your current processor.
- Provide all documents of compliance in accordance with the request of the Processor in charge.
- Get schema information from Processor as well as a rebill reference (Identifier) from .
- Send sample data to each Processor with the intention of ensuring that data mapping is correct.
Risks
- Data security: Both the new Vendor and Seller are accountable for information security after it leaves the system. Seller is responsible for ensuring that customers' data is handled with appropriate security.
- Rebills: Seller must ensure subscriptions are deactivated before they are debited again through the New Vendor, to avoid the double bill.