Charge

POST

Charge

Blinke Carrier Billing is an online payment method where you can simply charge an Indosat Ooredoo mobile phone number for a digital goods payment.

 

There are 2 APIs required for Carrier Billing:

  1. Request Code: Initiate the carrier billing payment to send a charging token through SMS to the user's mobile phone number. The token generated via the request code method will automatically expire after 5 minutes. (Read more)
  2. Charge: After the application user Returns the Token, the user is required to input the Token to your application. Your application will then need to perform a Send Charge Request to Blinke along with the token. If the Token is valid, the user will be charged to his Indosat mobile phone number balance. Upon successful charging, user will Return a SMS to confirm the amount that has been deducted.

 

To charge the Indosat Ooredoo mobile phone number, the request must pass in the access_token value in the header along with token code that is sent to user mobile phone number. For more information on how to generate your access_token, please refer to this section.

 

 

Request

Method URL
POST https://blinke-stage.apigee.net/cb/charge

 

 

Request Headers

Name Description Mandatory
Authorization Bearer access_token Yes
Content-Type application/json Yes

 

 

Request Body

Request body is a JSON formatted text containing the following fields:

Name Description Mandatory
msisdn
string
Indosat Ooredoo mobile phone number to be charged. Format with msisdn e.g., 628150000001 (MSISDN format). Yes
uniqueId
string
A unique identifier provided by client (e.g.: transaction id). Yes
transCode
string
A valid transaction code taken from Request Code command. Yes
userCode
string
An valid code that entered by subscriber, this code is generated by Blinke system through Request Code command. Yes

 

 

Response

Result of the successful request contains following information:

Name Description
success
boolean
Return true if success.
transId
string
The Transaction ID from Blinke API.
message
string
The message information if the charging has been successfully processed.

 

 

Response (Example)

HTTP Code Response
200
{
    "transId": "1510529442266543808683470",
    "success": true,
    "message": "Charging is successful"
}
400
{
    "success": false,
    "error": {
        "code": "CB-104",
        "message": "Invalid subscriber number or MSISDN (e.g. valid prefix number: 628xxx)"
    }
}

Depending on the request, other error code may occurs. Please refer to the following error code:

  • CB-102 : Invalid session. This might due to the request takes too long to process.
  • CB-103 : Session not login. This might due to the request takes too long to process.
  • CB-104 : Invalid subscriber number or MSISDN (e.g. valid prefix number: 628xxx)
  • CB-105 : Invalid unique id
  • CB-106 : Code not sent
  • CB-107 : Invalid code
  • CB-108 : Invalid uid
  • CB-109 : Invalid sid or product id
  • CB-114 : Insufficient funds/balance
  • CB-115 : Charging fail
  • CB-116 : Charging fail : Invalid MSISDN
  • CB-130 : Over limit
  • CB-197 : Permission denied
401
{
    "fault": {
        "faultstring": "Invalid Access Token",
        "detail": {
            "errorcode": "keymanagement.service.invalid_access_token"
        }
    }
}

 

 

Sandbox limitation
  • Limited to 10 requests per developer.
  • The remaining request balance can be observed from Available-CB-Request-Quota response header.

Resource URL

https://blinke-stage.apigee.net /cb/charge

Header Parameters


Name Values Description
Content-Type
(required)

JSON

Authorization
(required)

Bearer access_token

Body Parameters


Name Values Description
Msisdn

TransID & Msisdn

Request Body

HTTP Basic

OAuth 2.0

API Key

Reset

Make a request and see the response.

Make a request and see the response.

Make a request and see the response.

Resource Summary

Security

Content Type

application/json

Working...