Subscriber Export Process -
STAKEHOLDERS
Internal
- Product Team and Payments
- CSM and Support
External
- Customer/Seller
- New Vendor
- Present 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 the ability to extract their subscription details which we store in our database and then give the token over to the New Vendor. This usually takes around up to 10 weeks.
PURPOSES
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 and the data is transferred, the Seller is responsible for subscription deactivation on the System to avoid any stray billings or customers' complaints.
SCOPE
- Transmitting active subscriber data to Seller.
- Coordinating with our current Payment Processor as well as our Seller's New Vendor to facilitate the migration of payment tokens.
- Migrating only Credit Card tokens; due the compliance requirements and rules the company is unable to transfer PayPal tokens.
PROCEDURE
Subscription migration involves the following five actions:
- They will offer active subscribers as well as list of subscribers, based upon payment method type and Processors.
- will provide the processor with a signed Letter of Interest (LOI) for the processing company, indicating the export of the token to the New Vendor. LOI varies in Processor to Processor.
- Connect the Seller, new Vendor, and current payment processor to enable token movement.
2.a. Current Processor will verify the AOC as well as other PCI related information of the New Vendor.
2.b. Once PCI verification Processor has been completed We will then provide the New Vendor with appropriate information about the next steps of moving and the timeline, which comprises (but does not limit itself to):
- A specific protocol for processing to send and receive token files. The process could also require sharing PGP keys (Public).
- Schema for the file the vendor should expect as well as the appropriate mapping ( will include the key or attribute to the tokens).
- Specific steps taken by the processor to encode and decrypt the information.
- Tokens will be transferred to the new Vendor through the current Processor.
- Seller will deactivate the active subscription to avoid double charges.
PREREQUISITES
- New Vendor's website is PCI certified.
- If receiving PAN numbers, further security measures as directed by the Processor needs to be taken.
- Store to which the subscription must be transferred.
- Date of expected migration and the last payment.
LIABILITY
- :
- Connect new Vendors and Sellers with current Processors.
- Send a Letter of Intent to each Processor.
- The share details of active subscribers, separated by Processor.
- Share the rebill reference, that will serve as a identifier for mapping the tokens.
- Seller:
- Give new Vendor contacts and furnish the appropriate documentation to demonstrate compliance.
- 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 requirements.
- Receive Letter of Intent and begin to release tokens to New Vendor.
- Work With New Vendor for data transfer and provide schema to the New Vendor.
- New Vendor:
- Connect to the current processor.
- Complete all compliance documentation according to the requirements of the current Processor.
- Get schema information from Processor as well as a rebill reference (Identifier) to .
- Distribute sample data from each processor to ensure appropriate data mapping.
Risks
- Security of data: The new Vendor and Seller are accountable for security of data once it has left the system; Seller must ensure that the final customer's data is dealt with with appropriate security.
- Rebills: Seller should ensure that subscriptions have been cancelled prior to being charged again by the New Vendor, to avoid double re-bill.