Perform validation

Introduction

Perform validation is initiated through HTTPS POST request by using URLs and the parameters.

Connecting Party’s app sends cardholder, device, session data and other parameters straight to Billblend to check the card for being valid.

A lot of criteria checks and filters may be applied, such as BIN, currency, country, blacklisted or not, etc. Depending on the integration, these settings may be customizable.

API URLs

IntegrationProduction
https://sandbox.billblend.com/checkout/dapi/v1/verification/{endpointId}/{invoiceId}https://pay.billblend.com/checkout/dapi/v1/verification/{endpointId}/{invoiceId}

Request Parameters

Parameter NameDescriptionValue
consumer Necessity: RequiredTypeObject
consumer.device Necessity: RequiredTypeObject
consumer.device.serialNumberConsumer’s device serial number.Necessity: RequiredType: StringLength: 1-50
consumer.emailСonsumer’s email address.Necessity: RequiredType: StringLength: 3-128
session Necessity: RequiredTypeObject
session.accessTokenAccess token key received in Optional consumer authentication.Necessity: RequiredType: StringLength: 32-128
session.nonceValue received in Initial verification response.Necessity: RequiredType: StringLength: 32-128
session.signatureValue received in Initial verification response.Necessity: RequiredType: StringLength: 32-128
sourceCard Necessity: RequiredTypeObject
sourceCard.expiry Necessity: RequiredTypeObject
sourceCard.expiry.monthSource Card expiration month.Necessity: RequiredType: IntegerLength: 2
sourceCard.expiry.yearSource Card expiration year.Necessity: RequiredType: IntegerLength: 4
sourceCard.holder Necessity: RequiredTypeObject
sourceCard.holder.firstNameCardholder’s first name.Necessity: RequiredType: StringLength: 1-50
sourceCard.holder.lastNameCardholder’s last name.Necessity: RequiredType: StringLength: 1-50
sourceCard.holder.printedNameCardholder’s printed name (first and last name together). May be used instead of firstName + lastName.Necessity: RequiredType: StringLength: 1-50
sourceCard.numberSource card number (PAN).Necessity: RequiredType: StringLength: 9-19
sourceCard.securityCodeSource card security code (CVV).Necessity: RequiredType: StringLength: 3-4
transaction Necessity: RequiredTypeObject
transaction.currencyUpper case letters (ISO 4217 alpha code).Necessity: RequiredType: StringLength: 3
location Necessity: OptionalTypeObject
location.latThe latitude specified in the range of -90.0 through +90.0, both inclusive.Necessity: OptionalType: Double
location.lngThe longitude specified in the range -180.0 through +180.0, both inclusive.Necessity: OptionalType: Double
billing Necessity: OptionalTypeObject
billing.address Necessity: OptionalTypeObject
billing.address.cityCity name.Necessity: OptionalType: StringLength: 1-100
billing.address.countryISO alpha3 country code.Necessity: OptionalType: StringLength: 3
billing.address.postcodeZipZIP post codeNecessity: OptionalType: StringLength: 1-10
billing.address.stateState is used if present. For example, Los Angeles is in CA state.Necessity: OptionalType: StringLength: 2-3
billing.address.streetStreet is used for district names and street names.Necessity: OptionalType: StringLength: 1-50
billing.address.street2Street 2 is used for long addresses. Usually it contains apartment and building №.Necessity: OptionalType: StringLength: 1-50
billing.phoneCustomer’s contact phone number.Necessity: OptionalType: StringLength: 1-20
consumer.birthDayСonsumer’s birth day in “ddMMyyyy” format.Necessity: OptionalType: StringLength: 8
consumer.device.imeiСonsumer’s device international mobile equipment identity.Necessity: OptionalType: StringLength: 14-16
consumer.ipAddressesСonsumer’s IP addresses.Necessity: OptionalType: List
consumer.ipAddresses[]Сonsumer’s IP address.Necessity: OptionalType: StringLength: 7-15
order Necessity: OptionalTypeObject
order.descriptionBrief transaction description. May be mandatory for certain Acquirer Banks.Necessity: OptionalType: StringLength: 128
order.siteUrlURL of website associated with the transaction.Necessity: OptionalType: StringLength: 128
order.purposeMay be used for better transaction control or additional checks.Necessity: OptionalType: StringLength: 128

Success Response Parameters

Parameter NameDescriptionValue
invoiceIdVerification transaction identifier.Type: String
session TypeObject
session.tokenThe session token of verification transaction.Type: String

Fail Response Parameters

Parameter NameDescriptionValue
error TypeObject
error.causeCause of the error. Possible values: INVALID_REQUESTINVALID_CONFIGURATIONINTERNAL_ERRORPROCESSING_FAILED.Type: Enum
error.codeThe unique error code.Type: String
error.messageDescription of the error.Type: String
invoiceIdVerification transaction identifier.Type: String

Request Example

{
  "billing": {
    "address": {
      "city": "string",
      "country": "string",
      "postcodeZip": "string",
      "state": "string",
      "street": "string",
      "street2": "string"
    },
    "phone": "string"
  },
  "consumer": {
    "birthDay": "string",
    "device": {
      "imei": "string",
      "serialNumber": "string"
    },
    "email": "string",
    "ipAddresses": ["string"]
  },
  "location": {
    "lat": "double",
    "lng": "double"
  },
  "order": {
    "description": "string",
    "siteUrl": "string",
    "purpose": "string"
  },
  "session": {
    "accessToken": "string",
    "nonce": "string",
    "signature": "string"
  },
  "sourceCard": {
    "expiry": {
      "month": "integer",
      "year": "integer"
    },
    "holder":{
      "firstName": "string",
      "lastName": "string"
    },
    "number": "string",
    "securityCode": "string"
  },
  "transaction": {
    "currency": "string"
  }
}

Success Response Example

{
  "invoiceId": "string",
  "session": {
    "token": "string"
  }
}

Fail Response Example

{
  "error": {
    "cause": "enum",
    "code": "string",
    "message": "string"
  },
  "invoiceId": "string"
}

Request Builder

Request Builder is available at this link – https://doc.billblend.com/integration/API_commands/api_mobile_device/api_perform_validation.html#request-builder

 

 

Contact us

By clicking on the button, you agree to the data protection policy

Complete the quiz

By clicking on the button, you agree to the data protection policy