Get Consent Initiations Request

get https://test-api.tbcbank.ge/xs2a-sandbox/v2/{extended-payment-service}/{payment-product}/{paymentId}/initiations

time	status	user agent
Retrieving recent requests…

Loading…

Responses

Response body

object

paymentId

string

Resource identification of the generated payment initiation resource.

transactionStatus

string

The transaction status is filled with codes of the ISO 20022 data table: - 'ACCC': 'AcceptedSettlementCompleted' - Settlement on the creditor's account has been completed. - 'ACCP': 'AcceptedCustomerProfile' - Preceding check of technical validation was successful. Customer profile check was also successful. - 'ACSC': 'AcceptedSettlementCompleted' - Settlement on the debtor�s account has been completed. Usage: this can be used by the first agent to report to the debtor that the transaction has been completed.
Warning: this status is provided for transaction status reasons, not for financial information. It can only be used after bilateral agreement. - 'ACSP': 'AcceptedSettlementInProcess' - All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution. - 'ACTC': 'AcceptedTechnicalValidation' - Authentication and syntactical and semantical validation are successful. - 'ACWC': 'AcceptedWithChange' - Instruction is accepted but a change will be made, such as date or remittance not sent. - 'ACWP': 'AcceptedWithoutPosting' - Payment instruction included in the credit transfer is accepted without being posted to the creditor customer�s account. - 'RCVD': 'Received' - Payment initiation has been received by the receiving agent. - 'PDNG': 'Pending' - Payment initiation or individual transaction included in the payment initiation is pending. Further checks and status update will be performed. - 'RJCT': 'Rejected' - Payment initiation or individual transaction included in the payment initiation has been rejected. - 'CANC': 'Cancelled' Payment initiation has been cancelled before execution Remark: This codeis accepted as new code by ISO20022. - 'ACFC': 'AcceptedFundsChecked' - Preceding check of technical validation and customer profile was successful and an automatic funds check was positive . Remark: This code is accepted as new code by ISO20022. - 'PATC': 'PartiallyAcceptedTechnical' Correct The payment initiation needs multiple authentications, where some but not yet all have been performed. Syntactical and semantical validations are successful. Remark: This code is accepted as new code by ISO20022. - 'PART': 'PartiallyAccepted' - A number of transactions have been accepted, whereas another number of transactions have not yet achieved 'accepted' status. Remark: This code may be used only in case of bulk payments. It is only used in a situation where all mandated authorisations have been applied, but some payments have been rejected.

ACCC ACCP ACSC ACSP ACTC ACWC ACWP RCVD PDNG RJCT CANC ACFC PATC PART

transactionFees

object

currency

string

ISO 4217 Alpha 3 currency code.

amount

string

The amount given with fractional digits, where fractions must be compliant to the currency definition.
Up to 14 significant figures.
Negative amounts are signed by minus. The decimal separator is a dot.

currencyConversionFee

object

currency

string

ISO 4217 Alpha 3 currency code.

amount

string

estimatedTotalAmount

object

currency

string

ISO 4217 Alpha 3 currency code.

amount

string

estimatedInterbankSettlementAmount

object

currency

string

ISO 4217 Alpha 3 currency code.

amount

string

transactionFeeIndicator

boolean

If equals true, the transaction will involve specific transaction cost as shown by the ASPSP in their public price list or as agreed between ASPSP and PSU.If equals false, the transaction will not involve additional specific transaction costs to the PSUunless the fee amount is given specifically in the data elements transactionFees and/or currencyConversionFees.If this data element is not used,there is no information about transaction fees unless the fee amount is given explicitly in the data element transactionFees and/or currencyConversionFees.

scaMethods

array of objects

This data element might be contained, if SCA is required and if the PSU has a choice between different authentication methods. Depending on the risk management of the ASPSP this choice might be offered before or after the PSU has been identified with the first relevant factor, or if an access tokenis transported. If this data element is contained, then there is also a hyperlink of type "startAuthorisationWithAuthenticationMethodSelection"contained in the response body.These methods shall be presented towards the PSU for selection by the TPP.

scaMethods

object

authenticationType

string

Type of the authentication method. More authentication types might be added during implementation projects and documented in the ASPSP documentation. - 'SMS_OTP': An SCA method, where an OTP linked to the transaction to be authorised is sent to the PSU through a SMS channel. - 'CHIP_OTP': An SCA method, where an OTP is generated by a chip card, e.g. a TOP derived from an EMV cryptogram. To contact the card, the PSU normally needs a (handheld) device. With this device, the PSU either reads the challenging data through a visual interface like flickering or the PSU types in the challenge through the device key pad. The device then derives an OTP from the challenge data and displays the OTP to the PSU. - 'PHOTO_OTP': An SCA method, where the challenge is a QR code or similar encoded visual data which can be read in by a consumer device or specific mobile app. The device resp. the specific app than derives an OTP from the visual challenge data and displays the OTP to the PSU. - 'PUSH_OTP': An OTP is pushed to a dedicated authentication APP and displayed to the PSU. - 'SMTP_OTP': An OTP is sent via email to the PSU.

authenticationVersion

string

Depending on the "authenticationType".
This version can be used by differentiating authentication tools used within performing OTP generation in the same authentication type.
This version can be referred to in the ASPSP?s documentation.

authenticationMethod

string

An identification provided by the ASPSP for the later identification of the authentication method selection.

name

string

This is the name of the authentication method defined by the PSU in the Online Banking frontend of the ASPSP.
Alternatively this could be a description provided by the ASPSP like "SMS OTP on phone +49160 xxxxx 28".
This name shall be used by the TPP when presenting a list of authentication methods to the PSU, if available.

explanation

string

Detailed information about the SCA method for the PSU.

chosenScaMethod

object

authenticationType

string

authenticationVersion

string

authenticationMethod

string

An identification provided by the ASPSP for the later identification of the authentication method selection.

name

string

explanation

string

Detailed information about the SCA method for the PSU.

_links

object

scaOAuth

object

startAuthorisationWithPsuIdentification

object

self

object

status

object

scaStatus

object

psuMessage

string

Text to be displayed to the PSU

Language

URL


xxxxxxxxxx
1
curl --request GET \
2
     --url https://test-api.tbcbank.ge/xs2a-sandbox/v2/deferred-payments/aspsp/paymentId/initiations \
3
     --header 'accept: application/json'

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200OK

400Bad Request

500Internal Server Error