tbi bank – Integration specifications

1. Integration workflow:
   Integration is performed via APIm:
   – Authorize
   – RegisterApplication
   – ApplicationStatusNotification
   1.1. Integration diagram
   1.2 AuthorizeUAT environment:
   POST https://tbi-apim.azure-api.net/ftosgr/api/v1/User/authorize
   Host: tbi-apim.azure-api.net
   Headers:
   Content-Type: application/json
   Ocp-Apim-Subscription-Key: *************************
   Ocp-Apim-Trace: true
   Request example:

   Response example:
   Usage example:
   curlJqueryAuthorize Request
   
   1.3. RegisterApplication
   
   UAT environment:
   POST https://tbi-apim.azure-api.net/ftosgr/api/v1/Application
   Host: tbi-apim.azure-api.net

   Headers:
   Content-Type: application/json
   Ocp-Apim-Subscription-Key: ***************************
   Ocp-Apim-Trace: true
   AuthorizationToken: ff70ac71-fc25-4027-a3cb-d7afa380a422
   (Authorization token can be retrieved from response of Authorize method)

   Request example:

   Response example:

   NOTE:
   For the field Origin are applicable the below values:
   – "POS_Online " in case of the POS online standard products
   – "BNPL" in case of the BNPL products

   Usage example:
   curl
   
   

   

   Jquery

   
   
   

   1.4. Notifications statuses:
   a) Pos
   
   The endpoint where tbi's Back end will send the status of the application to the Merchants "statusurl"
   property when a new application is submitted (see API "Application" )

   UAT environment
   Request URL
   https://tbi-apim.azure-api.net/ftosgr/api/applicationstatus

   HTTP request
   POST https://tbi-apim.azure-api.net/ftosgr/api/applicationstatus HTTP/1.1

   Host: tbi-apim.azure-api.net
   Content-Type: application/json
   Ocp-Apim-Subscription-Key: ••••••••••••••••••••••••••••••••
   Ocp-Apim-Trace: true

   Response HTTP/1.1 200 OK

   Request to merchant.
   API management, having received a request, sends the same request to the merchant without any
   changes to the address from the "StatusUrl" field. The body of request is exactly the same, with no
   changes.

   b) Bankly
   
   1.5. Full return:
   POST https://tbi-apim.azure-api.net/ftosgr/api/v1/Application/return HTTP/1.1
   Host: tbi-apim.azure-api.net
   Content-Type: application/json
   AuthorizationToken: ******************
   Ocp-Apim-Subscription-Key: ********************
   Ocp-Apim-Trace: true

   HTTP/1.1 200 OK
   api-supported-versions: 1.0
   content-type: application/json; charset=utf-8
   date: Wed, 03 Aug 2022 09:49:25 GMT
   ocp-apim-apiid: ftos-greece
   ocp-apim-operationid: 62ea439a61f0848452aea5f6
   ocp-apim-subscriptionid: master
   ocp-apim-trace-location:
   https://apimgmtstid3lcsfdhczuwak.blob.core.windows.net/apiinspectorcontainer/I-i29bfMIRMHcduW2zgLA2-710?sv=2019-07-
   07&sr=b&sig=F8jLHj5tbEnVk0NGWkFdzvTjIzuPu7%2FskwQAkcdJg%2BM%3D&se=2022-08-
   04T09%3A49%3A25Z&sp=r&traceId=4b18576e36d242488559957a1893a34a
   request-context: appId=cid-v1:a03dab33-a837-493b-a0e2-233cd981e876
   transfer-encoding: chunked
   vary: Origin
   x-powered-by: ASP.NET

   1.6. Checking goods availability:
   When the request sent to [statusUrl] contains the Order Confirmation status ID, the merchant
   must respond:
   – with http status 200 (OK) when goods are available
   – with any of the 4xx or 5xx statuses when the goods are no longer available
   Send status example:
   POST [statusUrl]Content-Type: application/json
   Body:

   

   PROD environment: to be provided after set up on API'm
   
   RegisterApplicationRequest

   
   

   
   

2. Customer journey: All designs are responsive to screen resolution.
   Please find below our designs for the process (it is currently in progress development):
   
   
   
   

Κατεβάστε το εγχειρίδιο του API