Unbind API

Path/{version}/registration-account-unbinding
HTTP MethodPOST
Versionv1.0
SNAP service code09

Request Header

Field NameField TypeMandatoryField Description
Content-typeStringMMedia type of the resource, i.e. application/json
X-TIMESTAMPStringMClient’s current local time in ISO-8601 format
X-SIGNATUREStringMCreated using symmetric signature HMAC_SHA512 algorithm
AuthorizationStringMRepresents access_token of a request; string starts with keyword “Bearer ” followed by access_token. Can get this token from Access Token B2B API response.
Authorization-CustomerStringMRepresents access_token of a request; string starts with keyword “Bearer ” followed by access_token from Binding API response
X-PARTNER-IDStringMUnique identifier for merchant. Merchant can send any value.
X-EXTERNAL-IDStringMAlphanumeric string. We suggest merchant to use UUID format. Reference number that should be unique in the same day or 1 day idempotency key.
X-DEVICE-IDStringMDevice identification on which the API services is currently being accessed by the end user (customer)
CHANNEL-IDStringMMandatory field from Bank Indonesia that can take any value with correct format 5 digits numeric string
Content-type:application/json
Authorization: Bearer gp9HjjEj813Y9JGoqwOeOPWbnt4CupvIJbU1Mmu4a11MNDZ7Sg5u9a
Authorization-Customer : Bearer MjAyMjEwMTM2NjE1OGRiMS00NmM1LTQxMWQtYmU4NC01ODk1ZTdhMjg2NmY6OGNmM2U4NWUtZTc3Mi00NTJmLWFkYmEtNDcyNjRiOWZiZWIw
X-TIMESTAMP:2024-03-19T14:30:00+07:00
X-PARTNER-ID: BMRI
X-DEVICE-ID: 0987ADCASA
X-SIGNATURE: da1fa417c72d6b91c257e01e54fac824
X-EXTERNAL-ID:1234567890123456789
CHANNEL-ID:12345

Request Body

Field NameField TypeMandatoryField Description
merchantIdString (64)MMerchant ID (use the same value with merchantId in get-auth-code endpoint)

Merchant payment handle, merchant identifier in UUID format. Provided by Midtrans.
Note: this value is not Midtrans Merchant ID, but a different value, here's the sample format: 303b4f89-xxxx-xxxx-xxxx-62a8ffaefaf3

The value on staging and production is different. Please make sure that you are sending the correct value based on the environment that you are using.
{
   "merchantId":"M1234567890"
}

Response Header

Field NameField TypeMandatoryField Description
Content-typeStringMMedia type of the resource, i.e. application/json
X-TIMESTAMPStringMClient’s current local time in ISO-8601 format
Content-type: application/json
X-TIMESTAMP: 2024-03-19T14:30:00+07:00

Response Body

Field NameField TypeMandatoryField Description
responseCodeString(7)MError code to specify the error returned.
responseMessageString (150)MDebug message to provide more information.
referenceNoStringMDebug id to provide more information.
{
   "responseCode":"2000900", 
   "responseMessage":"Request has been processed successfully",
   "referenceNo":"19352694-0ef6-4439-8ad1-b1dfb8bbb85f"
}
{
   "responseCode":"5000900",
   "responseMessage":"Timeout",
   "referenceNo":"19352694-0ef6-4439-8ad1-b1dfb8bbb85f"
}

List of Response Code

Response CodeHTTP Status CodeResponse Message
2000900200Success
4000902400Invalid Mandatory Field
4010900401Unauthorized. Signature
4010900401Unauthorized. Incorrect merchantId value (return if merchant id value in request body not valid)
4010901401Invalid Token (B2B)
4010902401Invalid Customer Token
4040905404Merchant Is Not Registered For Card Registration Services
5000901500Internal Server Error
5040900504Timeout