Server to Server Callback Feature (Optional)

Besides the user browser redirection back to Service Provider, there will be server to server callback for IOD and subscription success charge transaction.

Service Providers need to provide this callback URL to BOOSTCONNECT operation during the onboarding process. The callback will be an HTTP POST call and JSON payload.

🚧

Callback to Service Provider

HTTP POST <Service Provider's callback URL for transaction status>

📘

Note

This callback feature will only happen for successful transactions and it’s optional.

Server to Server Callback for Service Provider

For IOD transactions, the server to server callback will be as below;

{ "data": 
{ 
    "transactionOperationStatus":"Charged", 
    "totalAmountCharged":"10.00", 
    "msisdn":"+60191234567", 
    "aocTransID":"12345678", 
    "clientCorrelator":"12345678901234567",
  "chargeMode":"standard",
    "errorCode":"00", 
    "errorMessage":"" 
} 
}

For subscription transactions, there will be 2 additional parameters (expiryDate and subscriptionID) returned which is as below;

{ "data": 
{ 
    "transactionOperationStatus":"Charged", 
    "totalAmountCharged":"10.00", 
    "msisdn":"+60191234567", 
    "aocTransID":"12345678", 
    "clientCorrelator":"12345678901234567", 
  "chargeMode":"standard",
    "expiryDate":"22-07-2020", 
    "subscriptionID":"Sub1", 
    "errorCode":"00", 
    "errorMessage":"" 
} 
}

📘

Note

For e-Wallet transactions, there will be no MSISDN return.

Server to Server Callback Feature for Split Charge

For Subscription under Split Charge (charge with minimum amount), the server to server callback will be as below;

{ "data":
{
    "transactionOperationStatus": "Charged",
    "totalAmountCharged": "5.00",
    "msisdn": "+60191234567",
    "aocTransID": "12345678",
    "clientCorrelator": "12345678901234567",
    "expiryDate": "22-07-2020",
    "subscriptionID": "Sub1",
    "chargeMode": "split",
    "errorCode": "00",
    "errorMessage": ""
}
}

For server to server callback for charge success on the remaining amount under Split Charge subscription will be as below;

{ "data": 
{
    "transactionOperationStatus": "Charged",
    "totalAmountCharged": "5.00",
    "msisdn": "+60191234567",
    "aocTransID": "12345678",
    "oriAocTransId": "T387487",
    "clientCorrelator": "12345678901234567",
    "expiryDate": "22-07-2020",
    "subscriptionID": "Sub1",
    "chargeMode": "split",
    "errorCode": "00",
    "errorMessage": ""
}
}

Server to Server Callback Feature for Step Down Charge

For Subscription under Step Down Charge (user choose step down option with lower amount and subscription duration), the server to server callback will be as below;

{   "data":
{
    "transactionOperationStatus": "Charged",
    "totalAmountCharged": "5.00",
    "msisdn": "+60191234567",
    "aocTransID": "12345678",
    "clientCorrelator": "12345678901234567",
    "expiryDate": "22-07-2020",
    "subscriptionID": "Sub1",
    "chargeMode": "stepdown",
    "subscriptionDuration":"8",
    "errorCode": "00",
    "errorMessage": ""
}
}

Server to Server Callback Feature for Parking Logic

For server to server callback for charge success on the recoup amount for subscription fee under Parking Logic will be as below;

{ "data": 
{
    "transactionOperationStatus": "Charged",
    "totalAmountCharged": "5.00",
    "msisdn": "+60191234567",
    "aocTransID": "12345678",
    "oriAocTransId": "T387487",
    "clientCorrelator": "12345678901234567",
    "expiryDate": "22-07-2020",
    "subscriptionID": "Sub1",
    "chargeMode": "standard",
    "errorCode": "00",
    "errorMessage": ""
}
}

📘

Note

The chargeMode value could be “standard”, “split” or “stepdown”. If it’s stepdown, the subscriptionDuration will be included as well.