Confirm Merchant Activation

POST

/v2.0/crm/merchant/confirmActivation

PSP (Non-FI) only.

Completes the Non-FI merchant activation flow. Submits the OTP received by the end-user together with the T&C ID obtained from initiateActivation (or getTnc). On success the merchant moves to ACTIVATED and the following fund APIs become available: createCryptoWithdrawal, createWithdrawal, sameNameWithdrawal/activate, createConversion.

internalTransfer remains permanently blocked for Non-FI partners regardless of activation status.

The result is synchronous 鈥� no webhook is emitted. An incorrect or expired OTP returns 400. Once activated, subsequent calls are idempotent and return ACTIVATED. acceptedTnC must contain the tncId returned by initiateActivation.

Request

Authorization

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Body Params application/jsonRequired

Example

{
    "participantCode": "B0100106",
    "otp": "482915",
    "acceptedTnC": [
        "N001"
    ]
}

Request Code Samples

Shell

JavaScript

Java

Swift

PHP

Python

HTTP

Objective-C

Ruby

OCaml

Dart

curl --location '/v2.0/crm/merchant/confirmActivation' \
--header 'Content-Type: application/json' \
--data '{
    "participantCode": "B0100106",
    "otp": "482915",
    "acceptedTnC": [
        "N001"
    ]
}'

Responses

🟢200Success

application/json

Bodyapplication/json

Example

{
    "code": 0,
    "msg": "string",
    "data": {
        "participantCode": "string",
        "activationStatus": "NOT_ACTIVATED",
        "activatedAt": 0
    }
}

Modified at 2026-07-24 05:46:59

Initiate Merchant Activation

Merchant Status Webhook