The API request consists of four steps: Method
Request Method: POST
The API is accessed from the Request URL. This is a combination of our URL and the addition of the following text at the end of the URL: “/v1/authorization/”
URL For Stage Environment:
URL For Production Environment:
Fill in the appropriate header information. The API Header information is provided by the iSignthis Merchant Support team.
||API client name
||Bearer API token
In order to generate the “Transaction API call”
the following API Objects
are required. Each object has a number of specific attributes in order to be successful.
Below you can view each object name, description and whether is required or not. Also, the glossary column has a link that directs you to detailed information about each object, including examples.
*Cardholder object is only applicable if you have card numbers entered on your own payment page (Server to Server). You must be PCI certified to do this. iSignthis will need to review and approve the PCI documents in order to allow Server to Server integration.
In the API body request you need to add the “workflow name” and the“id” in the “merchant” object with the ones provided by merchant support.
” text should be replaced with the “workflow name”
provided by iSignthis Merchant support team.
“Test_Merchant” text should be replaced with the “merchant_id” provided by iSignthis Merchant support team.
The API call consists of required fields to proceed with the payment:
Please take a look at the JSON code with the title “Sample JSON body for Acquiring” provided for reference.
NOTE: In the “account” object – identifier is the customer ID that you assigned to your customer. Each “identifier” must be unique and paired with the customer for future transactions.