Our October release addresses three areas where payment processing typically slows down: manual wallet-address entry, minor underpayments that leave requests unresolved, and verifying callback data before processing. Here’s what’s new:
- Reown for the TRON Blockchain – 500+ wallets and TRX or USDT (TRC-20) payment approval without leaving the payment page
- Underpayment Tolerance for Fixed Amount Book – small shortfalls accepted instead of leaving requests stuck in Partially Paid
- Extended Signature for CRM Callbacks – every callback parameter signed for verification before the CRM acts
Reown for the TRON Blockchain
We’ve added the option to pay on the payment page directly from a crypto wallet on TRON – our main production blockchain. As a result, end clients can connect any of 500+ supported wallets and approve a TRX or USDT (TRC-20) payment in just a few clicks. The address and amount go straight to the wallet, so there’s nothing to copy or paste. Once approved, the transaction is credited in Match2Pay like any other deposit.
Benefits:
- Faster deposits: the client connects a wallet and confirms the payment without leaving the payment page.
- No input errors: the address and amount go to the wallet automatically, so there’s no risk of typos and copy-paste mistakes.
- Wide wallet coverage: 500+ wallets are supported, including popular TRON wallets such as MetaMask and TronLink.
- Desktop and mobile support: payments work with browser wallet extensions and mobile wallet apps alike.
- Higher conversion: a shorter checkout flow means fewer abandoned payments.
Availability: Live on the payment page for TRX and USDT (TRC-20), with no configuration required.
Underpayment Tolerance for Fixed Amount Book
Fixed Amount Book requests can now close automatically as fully paid when the client pays slightly less than the requested amount. Match2Pay Support sets an underpayment tolerance on the gateway as a percentage, a fixed USD amount, or both. If the shortfall falls within either threshold, the request is automatically set to Done/Fully Paid. The tolerance applies to the total of all payments made against the request, so it also works when the client pays in several transactions. It covers shortfalls caused by exchange-deducted network fees, small rounding differences, and exchange rate movements on non-stablecoin payments.
In practice:
- A merchant issues a request for USD 100. A client pays from an exchange that deducts a network fee, so USD 99.00 arrives. Previously, the request stayed Partially Paid, and Support had to change the status manually.
- With a 1% tolerance, the client receives a USD 100 request and pays USD 99.00. The request closes automatically as Done, the merchant receives a Fully Paid callback, and the client gets the service or product right away.
- With the same setup, a USD 98.99 payment stays Partially Paid because the shortfall exceeds the threshold.
Benefits:
- Instant fulfillment: the end client receives the service or product right away, even when the payment is slightly short.
- Less manual work: Support no longer has to change statuses by hand, and end clients raise fewer tickets.
- Flexible configuration: it’s possible to set a percentage threshold, a fixed USD threshold, or both, with either one being enough.
- Consistent statuses: the callback returns Done/Fully Paid, the payment page shows the payment as paid, and the client receives the Fully Paid email.
- Safe rollout: without a tolerance set, the gateway works exactly as before.
Availability: Configured by Match2Pay Support on request and applied only to requests created after it’s enabled. These settings aren’t visible in the merchant dashboard. The tolerated shortfall isn’t topped up, so the merchant’s balance is credited with only the amount actually received.
Extended Signature for CRM Callbacks
We’ve introduced the Extended Signature, which covers the entire body of every callback we send to the merchant’s CRM. This lets the CRM verify that every transaction parameter came directly from Match2Pay, including paymentId, txid, deposit address, finalAmount, and settlementAmount. The Extended Signature is included in every callback type: crypto deposits and withdrawals, Binance Pay deposits, and all status updates. Any parameters we add to callbacks in the future will be covered automatically.
In practice:
- A client requests a 500 USDT withdrawal, and the CRM holds the funds on their trading account. A callback with FAIL status arrives. The CRM verifies the Extended Signature before returning the funds, so it knows the status came from Match2Pay.
- A client makes another deposit under the same paymentId, e.g., to a static deposit address. Before crediting it, the CRM checks the signature and confirms the txid and finalAmount match what Match2Pay sent.
Benefits:
- Full verification: the signature covers every transaction parameter in the callback.
- Safe automation for every status: DONE, PENDING, DECLINED, FAIL, and all other statuses can be verified before the CRM acts on them.
- Transaction-bound security: each signature is unique to a single callback.
- Simple implementation: the CRM signs the raw body as received, with no need to rebuild number formatting or field order.
- Future-proof integration: new callback parameters are signed automatically, with no integration changes.
Availability: Added to all callbacks automatically, with no configuration required. Existing integrations keep working exactly as before.
