Account Payment Release Blockage
Service Description
Release Blockage Service is used to release the blockage and the order amount will be transferred into the firm account. It may be used for the stock management, by the firm. If the firm wants to check the stock availability of the product/service right after the customer approves the payment, firm is able to consume release the blockage service. After all, the payment amount will be transferred into the firm’s account, from the customer’s account.
To be able to consume this service, BlockageInd field should be filled with the value ‘Y’ at the Create QR service, for the desired order.
This API is in the cash management category
API Profile |
|
---|---|
Attribute |
Value |
Name | Release Blockage |
Version | V1 |
Synopsis | Release Blockage Service |
Description | Creates UID which represents order information |
Pre-Conditions | HTTP POST method is allowed only in Release Blockage service. |
Authentication | OAuth 2.0 with Client Credentials |
Before your application can access the API, it must obtain a new access token for each request. The access token can be used only one time.
Endpoint Definition
Release Blockage API’s development live and mock environments routing data.
EndPoint / DEVELOPMENT SANDBOX SERVICE |
|
---|---|
URI | /cashmanagement/v1/releaseBlockage |
Base URL | https://apis.garantibbva.com.tr |
Technology
Technology Stack / DESIGN TIME |
|
---|---|
Property | Value |
HTTP Call Method | POST |
Response Content Type | application/json |
Request
HTTP POST method is allowed only in Release Blockage service.
Arguments
The list of arguments by the Release Blockage service to be invoked.
Request Fields | Type | Description | Obligation |
---|---|---|---|
OrderID | String | The order/invoice number which is unique | Mandatory |
Sample request
{ "OrderID":"BlokeDeneme1" }
Response
The Release Blockage service returns the result.
Sample response
"result": { "code": 202, "info": "The request has been received" }, "response":{ "resultCode":"B001", "resultMessage":"İşleminiz tamamlandı" }
Response codes from Send Money service request
Code |
Description |
Type |
---|---|---|
200 | OK | SUCCESS |
405 | {http.method} Method Not Allowed | CALL METHOD ERROR |
400 | Invalid Request | MISSING PARAMETERS |
401 | Invalid Credentials | UNAUTHORIZED |
429 | API plan limit exceeded | RATE LIMITING |
500 | Internal Server Error | SYSTEM ERROR |
Return Messages
CODE |
RETURN RESPONSE |
---|---|
400 |
{ "result": { "code": 400, "info": "Invalid Request" } } |
401 |
{ "result": { "code": 401, "info": "Invalid Credentials" } } |
405 |
{ "result": { "code": 405, "info": "POST Method Not Allowed" } } |
429 |
{ "result": { "code": 429, "info": "API plan limit exceeded" } } |
500 |
{ "result": { "code": 500, "info": "Internal Server Error" } } |
Response Messages
CODE |
RETURN RESPONSE |
---|---|
400 |
{ "result": { "code": 400, "info": "Invalid Request" }, "response":{ "resultCode":"H009", "resultMessage":"Bloke zaten iptal edilmiş." } } |
400 |
{ "result": { "code": 400, "info": "Invalid Request" }, "response":{ "resultCode":"H010", "resultMessage":"Bloke iptali için statü uygun değil." } } |
400 |
{ "result": { "code": 400, "info": "Invalid Request" }, "response":{ "resultCode":"H001", "resultMessage":"Kurum kodu dolu olmalıdır." } } |
400 |
{ "result": { "code": 400, "info": "Invalid Request" }, "response":{ "resultCode":"H011", "resultMessage":"Sipariş/Fatura numarası dolu olmalıdır." } } |
400 |
{ "result": { "code": 400, "info": "Invalid Request" }, "response":{ "resultCode":"H012", "resultMessage":"Sipariş numarası dolu olmalıdır." } } |
-
API URL : https://apis.garantibbva.com.tr
-
-
-