STAKEHOLDERS  

   Internal  

• The Payments Team and the Products Team
• CSM and Support

   External  

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

   OVERVIEW  

When customers are producing a lot of new subscribers or want to transfer the active subscriber of the existing service to a existing Vendor We've got the ability to get their subscriber details, which we store within our databases. We then transfer the token onto the New Vendor. This usually takes around up about 10 to 14 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. When the data is transferred, and the data has been transferred and the data is transferred, the Seller is accountable for cancelling subscriptions in the System to prevent any unintentional billings or customers' complaints.

   SCOP  

• Transmitting active subscriber data for Seller.
• Coordination with our current Payment Processor along with our Seller's brand new Vendor to facilitate the migration to payment tokens.
• Migrating only Credit Card tokens; due to the rules and compliance requirements, this business is not able to transfer PayPal tokens.

   HTML1 PROCEDURE PROCEDURE  

Subscription migration involves five steps:

1. They'll provide active subscribers and a listing of subscribers in accordance with the type of payment processor and method of payment.
2. Processors must provide the processor with a certified Certificate of Intent (LOI) to the processing company, indicating the exchange of the token to the new Vendor. LOI differs from Processor to Processing.
3. The Seller may be connected with the newly launched Vendor and the current payment processors in order to facilitate the movement of tokens.

2.a. Current Processor will verify the AOC and any other PCI pertinent information about the New Vendor.

2.b. Following the PCI validation Processor's verification process is completed, we will be capable of providing the new Vendor with appropriate details regarding the next steps in moving along with the timeframe comprising (but doesn't limit itself to):

• A unique protocol for the transfer and receive token files. It could also be necessary to share PGP keys (Public).
• Schema for the file vendors must anticipate and include the proper mapping ( contains the key or attribute to the tokens).
• The specific steps that are taken by the processor in order to encode and decode the data.

1. Tokens will be transferred over to the new Vendor through the current Processor.
2. Seller can deactivate the active subscription in order to avoid the double charge.

   REQUIREMENTS  

• New Vendor's website has been PCI-certified.
• In the event that you receive PAN numbers, then additional security measures , as directed by the Processor should be followed.
• Store from which subscription is to be transferable.
• The date of the expected change as well as the last amount to be paid.

   LIABILITY LIABILITY  

1. :

• Create connections for new Sellers and Vendors that are not currently Processors.
• Send a letter of intention to each processor.
• Share details for active subscribers are separated out by Processor.
• Rebill references are shared in order to provide an identifier in mapping tokens.

1. Seller:

• Provide the new Vendor contacts , and provide the required documentation to demonstrate conformity.
• Set Cancellation/Deactivation date on the subscriptions they wish to migrate off of the System.

1. This is the Processor that permits the present:

• Contact New Vendor and confirming compliance requirements.
• Request the letter of intent. Then, begin to release tokens to New Vendor.
• Work with New Vendor for data transfer and supply schema to the New Vendor.

1. New Vendor:

• Connect to the processor of the moment.
• All documentation must be completed to ensure conformity with the specifications of the present Processor.
• Find the schema details from Processor and rebill Reference (Identifier) to .
• Distribute sample data from each processor to ensure appropriate data mapping.

   Risques  

• Data security Security data Vendor as well as the Seller are accountable to protect the information when it is removed from the data system. The Seller is responsible to assure that the buyer's private data is treated in a manner that is appropriate to the level of protection.
• Rebills: Seller must ensure subscriptions have been terminated prior to being invoiced again from that New Vendor, to avoid duplicate re-billing.

This article first appeared on this site

This post was posted on here