Webhook

The merchant must implement an HTTP POST endpoint to receive asynchronous notifications related to the final status of a subscription process (whether successful or failed).

Once the subscription process is completed by the processor, Monnet will send a POST request to the webhook url provided by the merchant in the subscription creation request.

The merchant must be prepared to receive the following payload:

📦 Request Payload (JSON)

{
  "subscriptionId": 6,
  "chargeType": "ON_DEMAND",
  "customerId": "006123061",
  "originType": "MOBILE",
  "statusDescription": "Subscription processing failed",
  "statusCode": "9051",
  "statusMessage": "Not sufficient funds"
}

Request

FieldDescription
subscriptionIdInteger
Unique subscription identifier
chargeTypeString
Charge type (ON_DEMAND, RECURRING, etc.)
customerIdString
Customer identifier associated with the subscription
originTypeString
Subscription source channel (WEB, MOBILE, etc.)
statusDescriptionString
Human-readable description of the processing result
statusCodeString
Processing status code (e.g., 0000 = success, other = error)
Ver Error Code
statusMessageString
Additional message complementary to the result

✅ Expected Webhook Response

The webhook should return HTTP 200 OK to confirm successful receipt of the notification.

🔐 Recommended Security

It is recommended to implement authentication (e.g., token or IP whitelisting) to ensure the notification's legitimacy.

Errors Code

Error CodeError Message
9003Invalid merchant
9025Unable to locate record on file
9034Suspected fraud
9035Transaction not found
9040Requested function not supported
9051Not sufficient funds
9052Non-existing current account
9054Expired card
9057Transaction not permitted to cardholder
9061Effective advance is exceeded
9062Restricted card
9064Exceeds Withdrawal Limit
9065Merchant has exceeded the number of daily transactions
9097Operation Timeout
9099Error
9000Succeeded