This endpoint takes in the 6-digit BIN of a card and returns the capabilities for that card (eg: RTP, FedNow). Any end user can check the capabilities for any BIN.

The response comes in the form of a number between 0 and 100 representing our level of confidence that capability is available at the bank associated with the car the BIN is provided for. 0 being not available, and 100 being available.

Sandbox Triggers

In SANDBOX ONLY you can use the below values for the bin field in the request to trigger specific capability matches.

• Use only one trigger per request
• Using a trigger results in that capability returning a 100 confidence value - others in the response will be 0
• Not using a trigger will result in all capabilities returning a 50 confidence value
• BINs starting with a 0 will return a 400 error

Request

Authorization / Authentication

Use a valid access token in an Authorization: Bearer request header.

See Authenticating with an Access Token for more details.

GET /0.2/check_card_capabilites HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
// if using OAuth2
Authorization: Bearer [GENERATED JWT TOKEN HERE]
// if using ECDSA
authsignature: [GENERATED AUTHSIGNATURE HEX STRING HERE]
usersignature: [GENERATED USERSIGNATURE HEX STRING HERE]

{
  "header": {
  "created": 1234567890, //required
  "app_handle": "<your app_handle>", //required
  "user_handle": "<user_handle>", //required
  "version": "0.2", 
  "reference": "<your unique id>"
  }, 
  "bin": "<6-digit BIN>" //required
}

***

HTTP/1.1 200 OK

//

{
  'success': True,
  'rtp_credit_confidence': <0-100>,
  'rtp_debit_confidence': <0-100>.
  'fednow_credit_confidence': <0-100>.
  'fednow_debit_confidence': <0-100>,
  'bank_name': "<name of the bank associated with the card>",
  'card_type': "<CREDIT, DEBIT, PREPAID, or null>",
  'bin': "<the BIN submitted>"
}

Request Attributes

Responses