MoneyPay

1

General Information

The MANY PAY payment method is based on P2P transfers of fiat currencies with compensation in USDT:

1.2. Client Currencies (Deposit/Withdrawal):
Selected based on the chosen GEO processing;
The main currency for merchant balances and settlements: USDT (TRC 20);
MCC code: Not applicable (Person-to-Person payments);
Traffic: Primary and secondary.

1.3. Settlement fee:
Fee: $2 per withdrawal;
Instant USDT deposit to the merchant’s balance after a successful order completion;
Instant withdrawal from the personal account without delays;
No hold for most methods and GEO processing.

1.4. Rolling reserve:
Interaction methodology is discussed individually with each merchant. It is used for rare merchant-selected processing methods with option of chargebacks from users or governed in interactions with the merchant.

1.5. Wide Selection of GEOs and Processing Methods:
Limits, rates, and methods for the required currencies are processed upon request. For most selected currencies, the rate is based on ByBit/Binance, with the P2P section of that currency, reflecting the actual exchange rate and value of USDT in the selected GEO.

1.6. Custom Dispute Resolution Policy:
Each merchant has a unique policy for resolving disputes, which minimizes risks and simplifies interaction.

2

Payment Rules

2.1. Payment Process:

The user visits the merchant’s website and clicks the “Top up personal account (Pay for goods/services, etc.)” button. Depending on the integration method with the merchant, the client may be redirected to a separate payment gateway page (redirect integration), or the further payment actions will be embedded directly into the payment module on the client’s website (host-to-host integration), or via a pop-up window (iframe integration). The next step is for the client to select the payment transfer method:

Intra-bank transfer;
Fast payment system (FPS);
Transfer from another bank (interbank transfer).

The client must then enter the last four digits of the card (in the case of FPS – the phone number or full name) from which they will send the transfer and click “Next.” After the invoice generating, the client has 15 minutes to complete the transfer and click “Payment completed.”

If the client transfers the full amount, the request will be automatically confirmed, and the client will be redirected back to the merchant’s site where the balance was refilled.
If the client transferred funds but:
Clicked the “Cancel” button;
Transferred funds later than the 15 minutes allocated for payment;
Paid again using the provided details;
The merchant must notify MANY PAY Support (your personal support chat in Telegram).
If the client transferred an amount different from what was indicated in the invoice:
The request will be reviewed manually
If the merchant’s website has a mechanism for processing the modified amount, the request will be marked as successful, and callback information about the actual payment amount will be sent;
A notification about this transaction will be sent to the corresponding support chat in Telegram.

2.2. Payment Comments:
It is strictly prohibited to include any comments in the payment transfer (unless specified by the method rules).

2.3. Fake Receipts:
Attempts to attach fake payment receipts will result in the payer’s account being blocked.

3

Merchant personal account

To access the merchant’s personal account, you need to contact our Telegram support team to generate a registration link for the merchant’s personal account.

Once registered in the merchant personal account, the following features are available:

General balance and balance per store;
Withdrawal/Top-up balance in USDT via the TRC 20 network;
View account history (inflow and outflow of funds from the personal account);
Detailed balance change history;
Detailed order history;
Create new stores and manage settings for each within a single account.

With redirect integration, store details (name, URL) will be displayed on the payment gateway.

The API key for integration can be found in the store settings section.

User settings with the ability to enable 2FA are also available.

4

Integration Methods

Redirect Flow:

The user clicks to top up their balance on the merchant’s website, enters the amount, and selects the MANY PAY payment method. They are then redirected to the payment gateway where the payment process takes place. This method is simpler for the merchant because API integration is easier than Host-to-Host (H2H), requiring only the creation of a new store in the dashboard and the integration of our API into their system (create an order, check status, process callbacks).

Host-to-Host (H2H) Flow:

This payment method is directly integrated into the merchant’s website. The integration is slightly more complex than the redirect method as the merchant must design their payment flow and integrate the client interaction API into their system. Technical consultation is available for this integration.

The payment flow for the client remains the same as with the redirect, but all steps must be integrated by the merchant into their system. API modifications can also be made as necessary (e.g., payment verification from a specific card linked to the user’s account).

5

Callback System

The callback parameters can transmit various payment information to the merchant’s site (e.g., the actual amount transferred by the client).

6

Payment Page

The first page of the payment gateway in the redirect system.

7

Compliance Payment Checks

Additional user and payment data verification can be integrated into the system if required. For example, matching data provided during registration on the merchant’s system with the payment method used for topping up. This verification is optional, at the discretion of the merchant.

Payment System for High-Risk Projects

Free connection