.. meta::
   :description: Development tools for Wiserpay Mobile Device Server API: helper utilities for signing, debugging and validating server-side mAPI requests.

.. _api_development_tools:

Development tools
#################


.. role:: ex

.. role:: code

Introduction
^^^^^^^^^^^^

.. _signature-computation:

Signature computation
^^^^^^^^^^^^^^^^^^^^^

| The signature is being used to ensure that it is Connecting Party (and not a fraudster) who sends the information to Wiserpay.
| Signatures in DAPI are computed using :code:`HMAC_SHA1` algorithm. Key is derived in the following way:
|

#. Take Connecting Party ControlKey
#. Remove dashes from it
#. Unhex the result to binary

| The correct signature values for all types of transactions supported by DAPI in the debugging tool below:
|

.. raw:: html
      :file: ../../_static/examples/dapi_Signature_debug.html

.. _sdk:

Example code and SDK
^^^^^^^^^^^^^^^^^^^^

| There are several solutions available on GitHub, which were developed for integration with Wiserpay 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>`_