Migrating rebills in Maxpay – Maxpay Help Center

In the world of online transactions, smooth payment processing is crucial. Sometimes, there may be a need for businesses to migrate the rebills within their PSP or from one PSP to another. Here is how both options can be conducted within Maxpay:

1. Migrating rebills from one acquirer to another within Maxpay

2. Migrating rebills from another PSP to Maxpay

3. Migrating rebills from another PSP to Maxpay (if the merchant is not PCI DSS compliant)

1. Migrating rebills from one acquirer to another within Maxpay

To migrate rebills from one bank to another in Maxpay, you will need to send your standard request for a rebill , and only change two parameters in the request:

"merchant_account" and "merchant_password" should be changed to the credentials of the account where you need to migrate rebills

"base_reference" should be included as an additional parameter. It should contain Maxpay's reference of the initial 3Ds transaction. This will ensure the the transaction will be recognized as valid by another acquirer.

Let's review this change in an example. Below is an example request of the rebill before the migration (*conditional fields may vary depending on your previous setup):

"api_version": 1,
"merchant_account": "Account_And_Bank_1_MP_TRX",
"merchant_password": "password123",
"transaction_unique_id": "sale_by_token_request",
"transaction_type": "SALE",
"amount": 9.99,
"currency": "EUR",
"first_name": "John",
"last_name": "Doe",
"card_holder": "John Doe",
"address": "123 Street name.",
"city": "New York",
"state": "New York",
"zip": "12100",
"country": "USA",
"user_phone": "+12025550000",
"user_email": "johndoe@test.com",
"user_ip": "127.0.0.1",
"token": "5524fa52-75d8-4c7a-84ec-039d-97ab6f",
"cof_type": "MIT"

And here is the example request for the migration of the same rebill to another acquirer:

"api_version": 1,
"merchant_account": "Account_And_Bank_2_MP_TRX",
"merchant_password": "password456",
"transaction_unique_id": "sale_by_token_request",
"transaction_type": "SALE",
"base_reference":"S3FF000000000000000",
"amount": 9.99,
"currency": "EUR",
"first_name": "John",
"last_name": "Doe",
"card_holder": "John Doe",
"address": "123 Street name.",
"city": "New York",
"state": "New York",
"zip": "12100",
"country": "USA",
"user_phone": "+12025550000",
"user_email": "johndoe@test.com",
"user_ip": "127.0.0.1",
"token": "5524fa52-75d8-4c7a-84ec-039d-97ab6f",
"cof_type": "MIT"

Before proceeding with the migration described above, please get in touch with the Support Team at support@maxpay.com or in the dedicated chat, as the migration might vary on different acquirers.

Please note that this type of migration requires sharing tokens between the old and new accounts on Maxpay's side. Please do not migrate rebills before receiving further notice from Maxpay's support team.

Note: If you are the merchant with the Hosted Payment Page integration type, the migration will be done from Maxpay's side and no actions are required from the merchant

2. Migrating rebills from another PSP to Maxpay

To migrate rebills from an entirely different PSP/Acquirer to Maxpay, you will need to tokenize the transaction first, and then send us the following request for rebill payment. Here is the flow of how that should be handled:

1. Send a Tokenize request with the user's card data (except CVV) and get the token for the card

2. Send a SALE by Token request for rebill, including the token you received after Tokenize request. You will also need to add two additional parameters to the request:

"custom_scheme_transaction_id" : "value" - Scheme Transaction ID refers to a unique identifier assigned to a specific transaction by a payment scheme or network (Visa, Mastercard, etc.). The value of Scheme Transaction ID is obtained from your previous provider for each successful transaction in order to migrate the rebills without issues.

"cof_type": "MIT" - MIT stands for Merchant Initiated Transaction. It is used in a request to indicate that the payment is a rebill.

An example of the request:

"api_version": 1,
"merchant_account": "Account_MP_TRX",
"merchant_password": "password123",
"transaction_unique_id": "sale_by_token_request",
"transaction_type": "SALE",
"amount": 9.99,
"currency": "EUR",
"first_name": "John",
"last_name": "Doe",
"card_holder": "John Doe",
"address": "123 Street name.",
"city": "New York",
"state": "New York",
"zip": "12100",
"country": "USA",
"user_phone": "+12025550000",
"user_email": "johndoe@test.com",
"user_ip": "127.0.0.1",
"token": "5524fa52-75d8-4c7a-84ec-039d-97ab6f",
"custom_scheme_transaction_id":"MDR638302HY8GD8"
"cof_type": "MIT"

3. Migrating rebills from another PSP to Maxpay (if the merchant is not PCI DSS compliant)

If you have no PCI DSS certification, you cannot store card details on your side. In this case, to transfer rebills from another PSP to Maxpay, we will need to establish a direct email communication between Maxpay and the PSP in question to discuss the transfer details. The PSP will securely send Maxpay all the required details of users and their cards via SFTP, along with the parameter Scheme transaction ID for each transaction.

After receiving the information, we will tokenize the card data and have the parameter 'token' and other details, which will be transferred to the merchant. You will need to send us the following payment request with all required fields, plus two additional parameters:

"cof_type": "MIT" - MIT stands for Merchant Initiated Transaction. It is used in a request to indicate that the payment is a rebill.

An example of the request:

Before proceeding with the migration described above, please get in touch with the Support Team at support@maxpay.com or in the dedicated chat, as the migration might vary on different acquirers.

1. Migrating rebills from one acquirer to another within Maxpay

2. Migrating rebills from another PSP to Maxpay

3. Migrating rebills from another PSP to Maxpay (if the merchant is not PCI DSS compliant)

Cookie preferences