Subscription Export Process -
STAKEHOLDERS
Internal
- Product Team and Payments
- CSM and Support
External
- Customer/Seller
- New Vendor
- Current Payment Processors(Cards only)
OVERVIEW
When a client churns or decides to move their current subscriber to the New Vendor, we have to export their subscription data which we store within our system. We then give the token over in the direction of the New Vendor. This usually takes around up to 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. After the data has been transferred to the new vendor, the Seller is the one responsible for cancellation of subscriptions on the System to avoid any stray refunds, and thus customer complaints.
Scope
- Handing over active subscriber information to Seller.
- Coordination with our current Payment Processor and the Seller's New Vendor to facilitate the migration of payment tokens.
- We are only transferring Credit Card tokens; due the compliance requirements and rules We are unable to migrate PayPal tokens.
PROCEDURE
The migration of subscriptions involves five actions:
- will provide active subscribers and subscriber lists, based on the type of payment method and processors.
- The Processor will send an official Letter of Intent (LOI) to the processor, informing them of the export of the token to the New Vendor; The LOI will differ from Processor from Processor to Processor.
- The Seller will be connected to the 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 then provide the New Vendor with appropriate information regarding the next steps to be taken in the transition and timeframes. This include (but does not limit itself to):
- A specific protocol for processing for sending and receiving token files. The process could also require the sharing of PGP keys (Public).
- Schema for the file vendors should be expecting as well as the appropriate mapping ( should provide the key/attribute for tokens).
- Specific steps taken by the processor to encode and decrypt data.
- Tokens will be handed over to the new Vendor through the Processor currently in place.
- Seller will deactivate the active subscription to avoid double charges.
PREREQUISITES
- The New Vendor has been certified 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 needs to be transferred.
- Expected date of migration and last charge.
RESPONSIBILITIES
- :
- Connect Sellers and New Vendors to current Processors.
- Provide Letter of Intent to every processor.
- Share details of the active subscribers, separated by Processor.
- Share the rebill reference, that will serve as a identifier for mapping the tokens.
- Seller:
- Give the latest Vendor contacts and furnish necessary compliance documents.
- Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.
- The Processor of the Present:
- Contact New Vendor and confirming compliance with the requirements.
- Get the Letter of Intent. Then prepare for releasing tokens for New Vendor.
- Coordinate With New Vendor for data transfer and supply schemas for that New Vendor.
- New Vendor:
- Connect to the current processor.
- Provide all documents of compliance in accordance with the request of the processor in the process.
- Receive schema information from Processor and Rebill Reference (Identifier) to .
- Distribute sample data from each Processor with the intention of ensuring that data mapping is correct.
RISKS
- Security of data: The new Vendor and Seller are accountable for data security once it leaves system. Seller should ensure that end customers' data is handled in a secure manner.
- Rebills Seller must ensure subscriptions have been cancelled prior to being renewed by the New Vendor, to avoid the double bill.