Signed Payload for Transfer Requests.
This feature adds additional layer of security to Requests made to our Transfer API. If enabled, all requests made must have a signature passed as a header.
Feature Affected: Transfer
Endpoint: {{baseUrl}}/transaction/transfer
Authentication Technique: HMAC
Hash Algorithm: sha256
Header Param: x-request-id
How this works:
SignKey Generation: You can generate your signKey from the Startbutton dashboard, and it will be unique to your account.
Payload Signing: Once the feature is enabled, you’ll need to use your signKey to sign the payload of any API Transfer request you make.
Signature Header: The signature(hash) is passed as a header param.
Verification: Upon receiving the request, Startbutton verifies the signature to ensure that the payload is authentic and hasn’t been tampered with during transit.
NOTE: month, day, hour, and minute should allow leading zeros when they are less than 10
so if minute = 2, it should be 02
Here is a sample code on how to generate the x-request-id
:
Last updated