BlackPay
Merchant Payment Collection & Transaction Management
BlackPay is a merchant payment management platform. Connect the supported merchant and payment accounts you already own, create payment requests from the dashboard or the BlackPay API, and let BlackPay track each request until a supported incoming payment is detected and recorded.
Read the Privacy Policy to learn how BlackPay uses and protects your data.
Overview
What is BlackPay?
BlackPay is a merchant payment management platform. A business connects the merchant or payment accounts it already owns, creates payment requests from the dashboard or through the API, and BlackPay tracks each request until a supported incoming payment is detected and recorded.
BlackPay does not replace your payment account. Payments are collected into your own connected account; BlackPay generates the payment request, hosts the payment page, performs matching against available transaction information, and stores the resulting transaction record.
In short
- Connect accounts you already own
- Create payment requests (dashboard or API)
- Detect supported incoming payments
- Keep one record per payment request
- Send status webhooks to your app
Workflow
How BlackPay works
Connect → Create payment request → Customer pays → Detect → Record
1. Connect a supported account
You connect a merchant or payment account that you already own — for example a Paytm Business account, a BharatPe merchant account, a FamPay account, or a plain UPI ID — using the connection method BlackPay supports for that account type.
2. Create a payment request
From the BlackPay dashboard or through the BlackPay API you create a payment request for a specific amount. BlackPay returns a hosted payment page with the payment details and QR information for the selected account.
3. The customer pays
Your customer completes the payment with the payment method supported by that merchant account. Money moves directly from the customer to your own connected account.
4. BlackPay detects the payment
While the request is open, BlackPay processes the transaction information available for the connected account and looks for an incoming payment that matches the request — using details such as amount, transaction reference or identifier (UTR), timestamp and the account the request was issued on.
5. A transaction record is created or updated
When a supported payment is detected, BlackPay creates or updates the matching transaction record and, if configured, sends a signed webhook to your server and redirects the customer to your return URL.
Connections
Supported merchant and payment accounts
You connect eligible accounts that you own and control. BlackPay is an independent software product and is not affiliated with, endorsed by, or an official partner of any of the companies named below.
Paytm Business
Merchant account you own, connected by you. Payment requests are issued against the UPI ID of that account.
BharatPe merchant
Connected with the account holder's own login. BlackPay re-syncs the merchant identity and reads the transaction information available to that account.
FamPay (email notification)
Optional. If you link a Google account, BlackPay reads only FamPay “payment received” notification emails to obtain the reference and amount for a pending request.
Any other UPI ID (SMS verification)
Add your own UPI ID and pair the BlackPay companion Android app on your phone, which forwards bank payment-credit SMS so a submitted reference can be verified.
Matching
Automatic payment detection
BlackPay can process supported transaction information from connected accounts and identify incoming payments using the details that are available. Matching information may include the payment amount, transaction reference or identifier (UTR), timestamp, and the connected account the payment request was issued on.
Availability and accuracy of detection depend on the account type and on the information the underlying provider exposes to the account holder. Where automatic detection is not available, a payment reference can be submitted on the payment page and verified against the information BlackPay has for that account. Detection is not guaranteed to be instant, and a payment request that is not matched within its validity window is marked failed or expired.
BlackPay only processes information that the account holder has explicitly connected and authorised. It does not access private banking data without authorisation.
Records
Centralised payment records
BlackPay keeps one record per payment request, with the information supported by the platform:
- Payment / order ID
- Amount
- Payment status
- Transaction reference (UTR)
- Created and updated time
- Connected account used
- Payment link / order reference
- Detection & matching status
Developers
BlackPay API
BlackPay provides APIs that let your application integrate payment collection and transaction management. Every capability listed here is implemented today and documented in the API reference.
Create a payment request
POST an amount and your own order reference with an API key; BlackPay returns a payment page URL and token.
Payment page & QR information
A hosted payment page is generated for the selected connected account, with QR and UPI intent details.
Check payment status
Poll a status endpoint for the current state of a payment request (pending, paid, awaiting verification, failed or expired).
Signed webhook callbacks
BlackPay can POST a status callback signed with an HMAC signature to your server, with retries.
Redirect URL
Send the customer back to a URL of your choice once the payment request reaches a final state.
Scoped API keys
Each API key can be limited to specific connected accounts and a payment page template, or rotate across all of them.
Popup self-checkout
A small JavaScript snippet opens the payment page in a popup and reports the result back to your page.
PHP integration kit
A ready-made PHP kit with order creation, status checks, callback handling and popup checkout examples.
Audience
Who BlackPay is for
Google data transparency
Why BlackPay uses Google account data
Google account access in BlackPay is optional and is used for one feature only: verifying payments received on a FamPay account that you connect yourself. BlackPay does not use Google Sign-In to log you in, and it does not request Google Drive, Calendar, Sheets, or Contacts data.
When you choose to link a Google account to a FamPay merchant account, BlackPay requests exactly two scopes: userinfo.email and gmail.readonly. Gmail is searched only while one of your payment requests is pending, and only for FamPay “payment received” notification emails, so the amount and transaction reference can be matched to that request.
BlackPay does not send, modify, or delete email; does not read unrelated messages; and never sells Google data, uses it for advertising, or uses it to train AI models. BlackPay’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. See the Privacy Policy for full detail.
| Google data requested | Why BlackPay needs it | How it is used, stored and revoked |
|---|---|---|
Email address.../auth/userinfo.email | To show which Gmail mailbox is linked to which FamPay merchant account, so you can confirm the correct account is connected. | Displayed in the Merchants screen of your dashboard. Stored with your merchant account record while the connection exists; deleted when you disconnect. Not shared with third parties. |
Read-only Gmail messages.../auth/gmail.readonly | To find FamPay payment-notification emails for a pending payment request and read the amount and transaction reference needed to confirm that payment. | Searched only while one of your payment requests is pending. Only the extracted amount, reference and timestamp are stored, on the transaction record. Message bodies are not retained; email is never sent, modified or deleted. Access tokens are encrypted at rest. Revoke any time from Merchants in the dashboard or at myaccount.google.com/permissions. |
Trust
Security & privacy
What we access and why
- Account details you enter — email, merchant labels, UPI IDs. Needed to create payment requests on the right account.
- Transaction information — amount, reference/UTR, timestamp and status of payments related to your requests. Needed to match payments and keep records.
- Optional Google (Gmail) read-only access — used solely to locate FamPay payment-notification emails while one of your payment requests is pending, and to read the amount and reference from them. Nothing else in the mailbox is used, and the data is never sold, used for advertising, or used to train AI models.
- Companion app SMS forwarding — optional; only bank payment-credit messages are forwarded, to verify a submitted reference.
Storage, retention and control
- Data is stored in our managed cloud database, scoped so that each account can read only its own rows; connected-account credentials and OAuth tokens are encrypted at rest.
- Records are retained while your account is active. Deleting a connected account removes its stored credentials or tokens.
- You can disconnect any account from Merchants in the dashboard, and revoke Google access at myaccount.google.com/permissions at any time.
- To request deletion of your account and associated data, contact support@mxpay.vip.
- We make no claim to any external security certification. Full details are in the Privacy Policy.
Important information
About BlackPay
BlackPay is a software platform for payment collection, transaction tracking, payment management and application integration.
BlackPay is not a bank and does not provide banking services. It does not issue bank accounts, and it does not hold, receive or settle customer funds — payments move directly from your customer to the merchant account you connected.
Payment processing is performed by the third-party providers behind your connected accounts. Availability and functionality therefore depend on the respective provider, your authorisation, your account type and the provider's applicable terms. BlackPay makes no regulatory or licensing claims beyond being a software product.
FAQ
Frequently asked questions
What is BlackPay?
BlackPay is a software platform for merchant payment collection and transaction management. It lets a business connect supported merchant or payment accounts, create payment requests, detect supported incoming payments, and keep organised transaction records.
How does BlackPay detect payments?
For each open payment request BlackPay looks at the transaction information available for the connected account and matches an incoming payment by amount, transaction reference or identifier, timestamp and the account used. Detection depends on the account type and on the information the provider makes available; it is not guaranteed for every account.
What accounts can I connect?
Merchant and payment accounts you own yourself: Paytm Business, BharatPe merchant, FamPay (using its notification emails), or any UPI ID verified through the BlackPay companion Android app.
Can I integrate BlackPay with my application?
Yes. BlackPay provides a REST API, signed webhooks, a popup checkout script and a PHP kit. See the documentation for endpoints and examples.
Does BlackPay hold customer funds?
No. Payments go directly from your customer to your own connected account. BlackPay never receives, holds or settles those funds.
How do I disconnect a connected account?
Open Merchants in the dashboard and delete the account. Stored credentials or tokens for that account are removed. A linked Google account can also be revoked at myaccount.google.com/permissions.
What does BlackPay do with Google account data?
If you link a Google account for FamPay, BlackPay requests read-only Gmail access and uses it only to find FamPay payment-notification emails while one of your payment requests is pending, and to read the amount and reference from them. That data is not sold, used for advertising, or used to train AI models, and you can disconnect at any time.