Development tools

Introduction

Signature computation

The signature is being used to ensure that it is Connecting Party (and not a fraudster) who sends the information to Billblend.

Signatures in DAPI are computed using HMAC_SHA1 algorithm. Key is derived in the following way:

1. Take Connecting Party ControlKey
2. Remove dashes from it
3. Unhex the result to binary

The correct signature values for all types of transactions supported by DAPI in the debugging tool below:             Initiate Verification response signature             Check Verification response signature             Initiate Sale response signature          Check Sale response signature             Initiate Transfer response signature          Check Transfer response signature             Card Mapping response signature     

AccessToken	Use your existing accessToken or make it  for new transaction
Serial number
Endpoint ID
Session nonce	Use your existing nonce or make it  for new transaction
Merchant’s invoice	Use your existing invoiceId or make it  for new transaction
Transaction currency	ISO 4217 alpha three-letter code
Merchant control key

String to sign

Signature

Example code and SDK

There are several solutions available on GitHub, which were developed for integration with Billblend on Android and iOS platforms via DAPI.

Connecting Party proxy server for Money transfer:

https://github.com/payneteasy/paynet-transfer-merchant-proxy

Android SDK of Java implementation for Money transfer:

https://github.com/payneteasy/dengisend-android-transfer-api

iOS SDK of Objective-C implementation for Money transfer:

https://github.com/payneteasy/payneteasyTransfer