> For the complete documentation index, see [llms.txt](https://docs.mehticpay.ng/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mehticpay.ng/readme.md).

# MehticPay Business API

Integrate business wallets, transfers, payment links, terminals and Web3 collections with MehticPay.

Build business payment integrations with the MehticPay public merchant API. Read balances and transactions, manage recipients and collection terminals, initiate transfers, create hosted payment links, and collect supported blockchain assets.

These guides are for developers integrating MehticPay into a merchant website or backend. Start with the integration path below, then use the endpoint reference for request fields, response shapes and errors.

## Choose an integration

| Goal                              | Guide                                                                    | API reference                                                                                                                |
| --------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| Read your business and balances   | [Quickstart](/getting-started/quickstart.md)                             | [Business](/api-reference/business.md), [wallets](/api-reference/wallets.md)                                                 |
| Pay bank recipients               | [Bank transfers](/transfers-and-web3/bank-transfers.md)                  | [Banks](/api-reference/banks.md), [beneficiaries](/api-reference/beneficiaries.md), [transfers](/api-reference/transfers.md) |
| Accept payments through a link    | [Collect payments](/accept-payments/collect-payments.md)                 | [Payment links](/api-reference/payment-links.md), [checkout](/api-reference/checkout.md)                                     |
| Open checkout on your website     | [Inline JavaScript checkout](/accept-payments/inline-checkout.md)        | [Inline checkout API](/api-reference/inline-checkout.md)                                                                     |
| Receive signed transaction events | [Business webhooks v1](/webhooks-and-reconciliation/webhooks-v1.md)      | [PHP and Node.js receivers](/webhooks-and-reconciliation/webhook-examples.md)                                                |
| Collect blockchain payments       | [Web3 collections](/transfers-and-web3/web3.md)                          | [Web3 API](/api-reference/web3.md)                                                                                           |
| Reconcile activity                | [Callbacks and reconciliation](/webhooks-and-reconciliation/webhooks.md) | [Transactions](/api-reference/transactions.md)                                                                               |
| Manage collection points          | [Terminal reference](/api-reference/terminals.md)                        | [Terminal wallets](/api-reference/wallets.md)                                                                                |

## Implement inline checkout

1. [Open checkout with JavaScript](/accept-payments/inline-checkout.md#website-integration): embedded SDK code, payload and callbacks. The browser SDK works with either PHP or Node.js backends.
2. [Verify payment on your server](/accept-payments/verify-payments.md): PHP/Laravel and Node.js code, credentials, saved-order checks and responses.
3. [Receive signed webhooks](/webhooks-and-reconciliation/webhook-examples.md): PHP and Node.js receivers, sample event, acknowledgments and duplicate handling.

## Prepare your integration

| Requirement                             | Purpose                                                                     |
| --------------------------------------- | --------------------------------------------------------------------------- |
| Confirmed API origin                    | Base URL for requests in the intended environment                           |
| Public checkout key (`mp_pk_...`)       | Browser checkout initialization; select the correct Test or Live key        |
| Private merchant client/secret          | Server-side API requests and payment verification                           |
| Webhook signing secret (`mp_whsec_...`) | Authenticate notifications received by your server                          |
| Saved order/reference                   | Compare expected amount, currency, environment and split before fulfillment |

Follow the [quickstart](/getting-started/quickstart.md) for your first server request. Read [authentication](/getting-started/authentication.md), [permissions](/getting-started/permissions.md) and [response/error handling](/getting-started/conventions.md) before implementing writes. Never use a public checkout key or webhook secret as merchant API credentials.

## API scope

The merchant integration endpoints start with `/api/merchant`. Supporting payer endpoints start with `/api/checkout` and do not require merchant credentials. Configure checkout keys, split groups and webhook endpoints in the business dashboard.

Confirm your API base URL with MehticPay before making requests. `https://docs.mehticpay.ng` hosts the documentation; it is not the API base URL. The examples deliberately use a configurable API origin. See [environments](/getting-started/environments.md).

## Reference and downloads

The API reference covers merchant accounts, wallets, transfers, payment links, public checkout and server-side payment verification. For recipient allocation and payout workflows, see [Split payments](/accept-payments/split-payouts.md). Download the [OpenAPI specification and Postman collection](/resources/downloads.md) for supported merchant and public checkout endpoints.

* [Response conventions and errors](/getting-started/conventions.md)
* [Data models](/api-reference/models.md)
* [OpenAPI specification and Postman collection](/resources/downloads.md)

All identifiers, names, addresses and amounts in examples are fictional. Contact **<technical@mehtictech.com>** for integration help and **<helpline@mehtictech.com>** for account access issues. Include the HTTP method, path, response status and transaction reference when reporting a problem; omit credentials and authentication codes.