> For the complete documentation index, see [llms.txt](https://docs.neox.vn/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neox.vn/docs/global/global-collections/integration/how-to-register.md).

# How To Register

Before calling any Global Collections API, the Merchant must activate the service and obtain API credentials on the Merchant Portal.

**Step 1:** Log in to the Merchant Portal.

**Step 2:** On the right pane, choose the **Global Collections service**, click the **START REGISTRATION** button, then click **SUBMIT** on the confirmation popup.

**Step 3:** Complete the Merchant KYB review. NeoX (with the partner provider) verifies the master merchant before the service is enabled.

**Step 4:** Retrieve the API integration credentials.

* Open the **Profile** section on the Merchant Portal.
* Copy the **client\_id** and **client\_secret** — these are used by the [API authenPlatform](/docs/global/global-collections/integration/api-authenplatform.md) endpoint to obtain a Bearer token.

**Step 5:** Set up webhook delivery to receive event notifications (recommended).

There is no self-service webhook-configuration screen on the Merchant Portal. Instead:

* For most event types, supply a `webhookUrl` field directly in the request body when calling the relevant Create endpoint (Onboard Sub-Merchant, Create Virtual Account, Register Beneficiary, Create Payout Request) — the URL applies to that request/entity.
* The collection-transaction event group (trade/platform collections and their refunds) is delivered to a URL and secret **pre-configured centrally** for your merchant account instead — contact NeoX to have this configured.

See [Event Notification](/docs/global/global-collections/integration/event-notification.md) for the full delivery mechanics and `secureHash` verification.

**Step 6:** Generate the encryption key pair for sensitive payloads (if applicable).

* Generate an RSA key pair and upload the **public key** on the Merchant Portal.
* Keep the **private key** secret — it is used to decrypt any sensitive data returned by the service.

Once the service is **ACTIVE** and credentials are issued, proceed to [Security Method](/docs/global/global-collections/integration/security-method.md).