Brankas menu
×

Statement Retrieval API v1.0.0

Brankas Statement endpoints enable fintechs and financial service providers to leverage customer transaction information and deliver highly personalized financial services and applications.

  • Host https://docs.brank.as

  • Base Path v1

You can use Brankas Statement for the following:

  • Credit scoring - With the right analytics (e.g. predicted income, transaction categorization) and financial service providers, customer transaction data can be used to generate a credit score that determines credit-worthiness for both personal (e.g. mortgage, auto loan, credit card, or salary loan) and business loans.
  • Financial management applications - Customer transaction data and bank statements can be used to enable financial management apps and services that help individual consumers keep track of their finances, identify discrepancies in billings, and file tax returns. Additionally, it helps businesses streamline their financial operations, especially in terms of generating transaction feeds for accounting purposes, and periodic account reconciliation.
  • Personalized cross-sell or upsell opportinities - Customer transaction data can be used to generate targeted financial product recommendations and marketing promotions based on analytics for increasing sales revenues.
  • Customer verification - Bank statement retrievals can help in validating relevant financial data points (e.g. name verification, income verification).

API Access

This section details the first steps you need to take to successfully launch Brankas Statement.

  • Environment
  • OAuth2 Client
  • API Token

API Statement Services

Using the Sandbox

We have set up a Sandbox environment to simulate Brankas API calls. In this environment, you may perform test API requests to Brankas Bank, a dummy bank.

Below are the details required to perform API test calls in the Sandbox environment. Sandbox: https://statement.sandbox.<CLIENT_NAME>.bnk.to

Initiate Statement Retrieval Initiates a request to the Statement retrieval service to capture and store all financial transactions that have occurred over the past 90 days across all of a user’s bank accounts enrolled in a bank’s online banking portal.

This holds the request information to fetch a list of all financial transactions across all of bank accounts that a user has enrolled with their online banking profile at a specified bank’s online banking portal.

FieldTypeDescription
bank_codeBankCodebank_code is the internal code (enum) used by the service to target a specific bank for the statement retrieval request.
credCredentialcred is the user internet banking account credentials or StatementService token ID.

Initiate Statement Retrieval Response This response holds the status information of the statement retrieval request.

FieldTypeDescription
statement_idStringstatement_id is the unique system generated identifier assigned to this specific statement retrieval request. Once a statement has been retrieved and stored, it can then be queried later on from storage by using this as the identifier.
statusStatement Retrievalstatus is the current retrieval status.
site_reponseStringsite_response is any relevant text returned by the target bank’s online banking portal as part of the Statement retrieval request.

Retrieve all statements Calling this endpoint retrieves all statements that have been captured and stored by the Retrieve Statement request.

Retrieve all statements response Returns all previous captured statements.

FieldTypeDescription
statusStatementStatusthe current status of the statement retrieval request.
statementidStringstatement_id is the unique system generated identifier assigned to this specific statement retrieval request.
bank_codeBankCode (enum)bank_code is the internal code used by the service to target a specific bank for the statement retrieval request.
start_dateTimestampstart_date reflects the timestamp / date of the earliest date up to which the bank provides recorded transaction data, relative to the current date. This differs from bank to bank and can range from 30 to 90 days worth of transaction records from the current date.
end_dateTimestampend_date reflects the timestamp / date of when the statement retrieval request was initiated.
account_statementStatementthe full list of transactions captured by the statement retrieval request.
errorStringerror message in the case the statement retrieval operation was unsuccessful.

Retrieve a specific Statement Retrieves the list of all financial transactions captured by the RetrieveStatement request.

Statements Request retrieves a list of all statements previously captured and stored by the RetrieveStatement request.

FieldTypeDescription
statement_idsStringstatement_ids is the unique system generated identifier assigned to specific retrieved statements, allowing them to be queried specifically from storage.

Statements Response returns the list of all financial transactions included in the requested statement_ids.

FieldTypeDescription
statusStatementStatusThe current status of the statement retrieval request.
statement_idStringstatement_id is the unique system generated identifier assigned to this specific retrieved statement.
bank_codeBankCode (enum)bank_code is the internal code used by the service to target a specific bank for the statement retrieval request.
start_dateTimestampstart_date reflects the timestamp / date of the earliest date up to which the bank provides recorded transaction data, relative to the current date. This differs from bank to bank and can range from 30 to 90 days worth of transaction records from the current date.
end_dateTimestampend_date reflects the timestamp / date of when the statement retrieval request was initiated.
account_statementsStatementThe full list of transactions captured by the statement retrieval request.
errorStringError message in the case the statement retrieval operation was unsuccessful.

Send Login OTP SendTFA submits a two-factor authentication code.

In case a specific bank requires end users to succeed on an TFA challenge to login into their online banking accounts, the POST Send Login OTP endpoint allows you to submit the OTP code supplied by the end user to successfully authenticate and grant access to their online banking accounts.

FieldTypeDescription
purposeTFAPurposepurpose defines what this TFA code should be used for. In order to retrieve statements, this should be set to BankCredentialLogin by default.
purpose_idStringpurpose_id should reflect the statement_id included in the response of the POST Initiate Statement Retrieval endpoint. This allows the service to determine which ongoing statement retrieval process the submitted TFA code should be paired with.
tokenStringtoken is the actual TFA / OTP code string the end user needs to submit as part of this statement retrieval request.

The Send OTP Login response contains the status information of the relevant TFA challenge.

FieldTypeDescription
statusOperationStatusstatus defines the result of the Send OTP Login request, indicating whether or not the TFA token was successfully submitted to the relevant bank or if the operation resulted in an error.
auth_statusTFAStatusauth_status defines the result of submitting the TFA code with the bank, indicating whether the challenge succeeded or failed.
status_msgStringstatus_msg is the bank-specific response to a failed TFA challenge, qualifying the cause of the failure (such as an invalid or incomplete TFA code)

Status and Errors

Our API endpoints perform several steps in order to acquire the correct data response, including login. As such, all of our API endpoints can return a common set of error responses. Below is a list of shared error responses from our endpoints that are unable to perform an action.

These errors can be due to a session no longer being available with the bank integration, possibly due to another session being created.

Internally, our systems communicate using gRPC, which comes with a standard set of status codes. These codes are mapped to our status and error responses in the StatementService endpoints.

You can find the latest list of codes here, but we have documented them below as well.

CodeNumberDescription
OK0Not an error; returned on success.
CANCELLED1The operation was cancelled, typically by the caller.
UNKNOWN2Unknown error. For example, this error may be returned when a Status value received from another address space belongs to an error space that is not known in this address space. Also errors raised by APIs that do not return enough error information may be converted to this error.
INVALID_ARGUMENT3The client specified an invalid argument. Note that this differs from FAILED_PRECONDITION. INVALID_ARGUMENT indicates arguments that are problematic regardless of the state of the system (e.g., a malformed file name).
DEADLINE_EXCEEDED4The deadline expired before the operation could complete. For operations that change the state of the system, this error may be returned even if the operation has completed successfully. For example, a successful response from a server could have been delayed too long.
NOT_FOUND5Some requested entity (e.g., file or directory) was not found. Note to server developers: if a request is denied for an entire class of users, such as gradual feature rollout or undocumented whitelist, NOT_FOUND may be used. If a request is denied for some users within a class of users, such as user-based access control, PERMISSION_DENIED must be used.
ALREADY_EXISTS6The entity that a client attempted to create (e.g., file or directory) already exists.
PERMISSION_DENIED7The caller does not have permission to execute the specified operation. PERMISSION_DENIED must not be used for rejections caused by exhausting some resource (use RESOURCE_EXHAUSTED instead for those errors). PERMISSION_DENIED must not be used if the caller can not be identified (use UNAUTHENTICATED instead for those errors). This error code does not imply the request is valid or the requested entity exists or satisfies other pre-conditions.
UNAUTHENTICATED16The request does not have valid authentication credentials for the operation.
RESOURCE_EXHAUSTED8Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.
FAILED_PRECONDITION9The operation was rejected because the system is not in a state required for the operation’s execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE: (a) Use UNAVAILABLE if the client can retry just the failing call. (b) Use ABORTED if the client should retry at a higher level (e.g., when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence). (c) Use FAILED_PRECONDITION if the client should not retry until the system state has been explicitly fixed. E.g., if an “rmdir” fails because the directory is non-empty, FAILED_PRECONDITION should be returned since the client should not retry unless the files are deleted from the directory.
ABORTED10The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. See the guidelines above for deciding between FAILED_PRECONDITION, ABORTED, and UNAVAILABLE.
OUT_OF_RANGE11The operation was attempted past the valid range. E.g. seeking or reading past end-of-file. Unlike INVALID_ARGUMENT, this error indicates a problem that may be fixed if the system state changes. For example, a 32-bit file system will generate INVALID_ARGUMENT if asked to read at an offset that is not in the range [0,2^32-1], but it will generate OUT_OF_RANGE if asked to read from an offset past the current file size. There is a fair bit of overlap between FAILED_PRECONDITION and OUT_OF_RANGE. We recommend using OUT_OF_RANGE (the more specific error) when it applies so that callers who are iterating through a space can easily look for an OUT_OF_RANGE error to detect when they are done.
UNIMPLEMENTED12The operation is not implemented or is not supported/enabled in this service.
INTERNAL13Internal errors. This means that some invariants expected by the underlying system have been broken. This error code is reserved for serious errors.
UNAVAILABLE14The service is currently unavailable. This is most likely a transient condition, which can be corrected by retrying with a backoff. Note that it is not always safe to retry non-idempotent operations.
DATA_LOSS15Unrecoverable data loss or corruption.

Send a statement retrieval request

Initiates a statement retrieval request.

curl -X POST \
	https://docs.brank.as/v1/statement-retrieval \
	-H 'Authorization: Bearer USE_YOUR_TOKEN' \
	-d '{
		"bank_code": "BankCode",
		"credential": {
			"credential_type": "CredentialType",
			"identifier": "string",
			"secret": "string"
		},
		"period_days": "int32",
		"start_date": "string",
		"end_date": "string",
		"account_number": "string",
		"api_credential": {
			"corporate_id": "string",
			"identifier": "string",
			"secret": "string"
		},
		"external_id": "string",
		"channel": "string",
		"": "map[string]string"
	}'

HTTP Request

POST https://docs.brank.as/v1/statement-retrieval

Body Parameters

NameTypeDescription
bank_codeBankCodeBankCode is the bank code (MANDIRI, BCA, etc).
credentialCredentialCredential is the internet banking account credential.
period_daysint32PeriodDays is the filter to search transactions that occurred over a given period. note: the behaviour of the search is depends upon each bank site.
start_datestringStartDate is the start date of the statement request Date/Time ranges should follow the YYYY-MM-DD convention
end_datestringEndDate is the end date of the statement request Date/Time ranges should follow the YYYY-MM-DD convention
account_numberstringAccountNumber is the bank account number
api_credentialAPICredentialAPICredential are the credentials to access the bank API
external_idstringExternalID represent an id that is passed by the api consumer to track the request
channelstringChannel represent source channel whether a statement request is initiated from
map[string]stringAdditionalFields are list of key value pair which is optional. This can be used to pass bank specific fields that differs from bank to bank
Objects
Credential
NameTypeDescription
credential_typeCredentialTypeCredentialType is the value of credential type.
identifierstringIdentifier is the credential identifier.
secretstringSecret is the credential secret.
APICredential
NameTypeDescription
corporate_idstringCorporateID is the banks unique id for the organization. if the bank provides a partner_id, then it should be used instead.
identifierstringIdentifier is the unique identifier for the credential
secretstringSecret is the secret for the credential
Enums
BankCode
ValueDescription
UNKNOWN_BANK
MANDIRI_PERSONAL
BCA_PERSONAL
BNI_PERSONAL
BRI_PERSONAL
BCA_CORPORATE
DUMMY_BANK_PERSONAL
BDO_PERSONAL
BPI_PERSONAL
KASIKORNBANK_PERSONAL
PNB_PERSONAL
UNIONBANK_PERSONAL
UNIONBANK_CORPORATE
METROBANK_PERSONAL
RCBC_PERSONAL
CredentialType

CredentialType is the credential type.

ValueDescription
EMAIL
Type_MSISDN
TOKEN
CLIENT_CREDENTIAL

Responses

Response body

NameTypeDescription
statement_idstringStatementId is the unique identifier for the statement request.
statusInitialStatementStatusStatus is the statement request status.
site_responsestringSiteResponse is an optional text response from the bank website.
challengeChallengeChallenge is an optional challange information from the bank website to be used for next 2FA request.
Objects
Challenge
NameTypeDescription
typeChallengeType
databytes
Enums
InitialStatementStatus
ValueDescription
UNKNOWN_InitialStatementStatus
RECEIVED
PENDING
TFA_AWAIT
LOGIN_ERROR
INITIATED
ChallengeType

ChallengeType for captcha or OTP challenge

ValueDescription
TEXTTEXT are challenges that are generally represented as strings.
IMAGEIMAGE are image-based challenges, for example a captcha image.
IN_APPIN_APP are challenges that happens offline and asynchronously outside our control for example, approvals from a user’s mobile device.
SMSSMS are SMS-based challenge codes.
MGENCODEMGENCODE or Mobile Generated Code, are usually challenge codes generated by bank applications.
HYBRIDHYBRID are bank-specific challenge types, for example, BCA requires a mix of the different types.
PINPIN are mostly static pin codes from banks, eg Metrobank’s passcode.

Example:

{
  "statement_id": "string",
  "status": "InitialStatementStatus",
  "site_response": "string",
  "challenge": {
    "type": "ChallengeType",
    "data": "bytes"
  }
}

Response codes

StatusDescription
200A successful response.
404Returned when the resource is not found.

Send a statement list request

Retrive the statements list request.

curl -X GET \
	https://docs.brank.as/v1/statements \
	-H 'Authorization: Bearer USE_YOUR_TOKEN'

HTTP Request

GET https://docs.brank.as/v1/statements

Responses

Response body

NameTypeDescription
statements[]StatementStatements are the statements that match the filters of a request.
next_page_tokenstringNextPageToken represents the pagination token to retrieve the next page of results. If the value is “", it means no further results for the request.
messagestringMessage is any message from the server that are not treated as an error.
Objects
Statement
NameTypeDescription
statusStatementStatus
statement_idstringStatementID is the statement identifier.
bank_codeBankCodeBankCode is the bank code.
start_dateTimestampStartDate is the start date of statement period.
end_dateTimestampEndDate is the end date of the statement period.
account_statements[]AccountStatementAccountStatements is the list of account statements.
errorstringError is the error message if the request failed.
requestTimestampCreate is the request timestamp.
createTimestampCreate is the creation timestamp.
external_idstringExternalID represent an id that is passed by the api consumer to track the request
channelstringChannel represent source channel whether a statement request is initiated from
countrystringCountry is the country code (ID, PH, TH)
is_idpboolIsIDP denotes that the request processed through PIDP
sub_statusStatementSubStatusStatementSubStatus denotes the granular status
updateTimestampUpdate is the updation timestamp.
is_notification_successboolIsNotificationSuccess denotes whether the notification posted is successful or not
site_responsestringSiteResponse is an optional text response from the bank website.
challengeChallengeChallenge is an optional challange information from the bank website to be used for next 2FA request.
shortcodestringshortcode represent a staticlink code to indicate the statement request initiated via static link
map[string]bytesAccountPdfs is the list of account statement pdf files indexed by account number.
Timestamp
NameTypeDescription
secondsint64
nanosint32
AccountStatement
NameTypeDescription
accountAccountAccount is the bank account information.
transactions[]TransactionTransactions is the list of transaction which occured over the period_days.
account_pdfsbytesAccountPdfs is the list of account statement pdf files.
Challenge
NameTypeDescription
typeChallengeType
databytes
Account
NameTypeDescription
account_idstringAccountID is the bank account firestore document identifier.
typeAccountType
owner_ids[]stringOwnerIds is the list of bank credential identifiers that own and have access to this account. The first in the list is the primary owner, and the list cannot be empty.
account_numberstringAccountNumber is the account number.
nickstringNick is an optional nickname for the account.
balanceAmountBalance is the account balance.
holder_namestringHolderName is the full name of the account holder. The format might change between banks.
bank_codeBankCodeBankCode is the Brankas bank code for the bank that holds the account.
Transaction
NameTypeDescription
transaction_idstringTransactionID is the transaction firestore document identifier.
dateTimestampDate is the transaction date.
typeTransactionTypeType is the value of the transaction type.
statusTransactionStatusStatus is the transaction status.
amountAmountAmount is the transaction amount.
descriptorstringDescriptor is the original bank descriptor.
match_idstringMatchID is a reference to related match data.
fromAccountFrom is the transaction source account.
toAccountTo is the transaction destination account.
fieldsTransaction_Fields
Amount
NameTypeDescription
curCurrencyISO4217Cur is the currency.
numstringNum is the numeric value.
Transaction_Fields
NameTypeDescription
namestringName is the Name of the other party.
memostringMemo is the user input on a memo line.
account_nostringAccountNo is the other party’s acount number.
companystringCompany is the virtual account company name.
Enums
StatementStatus
ValueDescription
UNKNOWN_StatementStatus
Status_PENDING
FAILED
COMPLETED
NOTIFIED
Status_RECEIVED
CANCELLED
INACTIVATED
BankCode
ValueDescription
UNKNOWN_BANK
MANDIRI_PERSONAL
BCA_PERSONAL
BNI_PERSONAL
BRI_PERSONAL
BCA_CORPORATE
DUMMY_BANK_PERSONAL
BDO_PERSONAL
BPI_PERSONAL
KASIKORNBANK_PERSONAL
PNB_PERSONAL
UNIONBANK_PERSONAL
UNIONBANK_CORPORATE
METROBANK_PERSONAL
RCBC_PERSONAL
StatementSubStatus
ValueDescription
UNKNOWN_StatementSubStatus
SubStatus_INITIATEDInitiatated a request for PIDP
SubStatus_LOGIN_ERRORLogin Error
SubStatus_AWAITING_LOGINLogin in progress.
SubStatus_AWAITING_TFAAwaiting login TFA Authentication.
SubStatus_COMPLETEDSuccessful operation
SubStatus_BLOCKEDBlocked
SubStatus_INPROGRESSStatement retrieval in progress
SubStatus_INVALID_TFAInvalid TFA
SubStatus_NO_TFA_PROVIDEDNo TFA Provided
SubStatus_SYSTEM_UNAVAILABLESystem busy or unavailable to process the request
SubStatus_ERRORError
SubStatus_CANCELLEDCancelled
SubStatus_INACTIVATEDInactivated
ChallengeType

ChallengeType for captcha or OTP challenge

ValueDescription
TEXTTEXT are challenges that are generally represented as strings.
IMAGEIMAGE are image-based challenges, for example a captcha image.
IN_APPIN_APP are challenges that happens offline and asynchronously outside our control for example, approvals from a user’s mobile device.
SMSSMS are SMS-based challenge codes.
MGENCODEMGENCODE or Mobile Generated Code, are usually challenge codes generated by bank applications.
HYBRIDHYBRID are bank-specific challenge types, for example, BCA requires a mix of the different types.
PINPIN are mostly static pin codes from banks, eg Metrobank’s passcode.
AccountType

AccountType is the account type enum.

ValueDescription
UNKNOWN_AccountType
CHECKING
SAVINGS
TransactionType

TransactionType is the transaction type enum.

ValueDescription
UNKNOWN_TYPE
CREDIT
DEBIT
TransactionStatus

TransactionStatus is the transaction status enum.

ValueDescription
UNKNOWN_STATUS
SUCCESS
TRANSACTIONSTATUS_PENDING
CurrencyISO4217

CurrencyISO4217 iso is the 3 digit currency that will be used as standard currency type on fast checkout. see: https://en.wikipedia.org/wiki/ISO_4217

ValueDescription
UNKNOWN_CURRENCY
AFN
EUR
ALL
DZD
USD
AOA
XCD
ARS
AMD
AWG
AUD
AZN
BSD
BHD
BDT
BYR
BZD
XOF
BMD
BTN
BOV
BAM
BWP
NOK
BRL
SGD
BGN
BIF
KHR
XAF
CAD
CVE
KYD
CLP
CNY
COP
KMF
CDF
NZD
CRC
HRK
CUC
CZK
DKK
DJF
DOP
EGP
ERN
ETB
FKP
FJD
XPF
GMD
GEL
GHS
GIP
GTQ
GBP
GNF
GYD
HNL
HKD
HUF
ISK
INR
IDR
IRR
IQD
IMP
ILS
JMD
JPY
JEP
JOD
KZT
KES
KPW
KRW
KWD
KGS
LAK
LBP
LSL
LRD
LYD
CHF
MKD
MGA
MWK
MYR
MVR
MRO
MUR
MXN
MDL
MNT
MAD
MZN
MMK
NAD
NPR
ANG
NIO
NGN
OMR
PKR
PGK
PYG
PEN
PHP
PLN
QAR
RON
RUB
RWF
WST
STD
SAR
RSD
SCR
SLL
SBD
SOS
ZAR
SSP
LKR
SHP
SDG
SRD
SZL
SEK
SYP
TWD
TJS
TZS
THB
TOP
TTD
TND
TRY
TMT
UGX
UAH
ARE
UYU
UZS
VUV
VEF
VND
YER
ZRN
ZMW

Example:

{
  "statements": [
    {
      "status": "StatementStatus",
      "statement_id": "string",
      "bank_code": "BankCode",
      "start_date": {
        "seconds": "int64",
        "nanos": "int32"
      },
      "end_date": {
        "seconds": "int64",
        "nanos": "int32"
      },
      "account_statements": [
        {
          "account": {
            "account_id": "string",
            "type": "AccountType",
            "owner_ids": "[]string",
            "account_number": "string",
            "nick": "string",
            "balance": {
              "cur": "CurrencyISO4217",
              "num": "string"
            },
            "holder_name": "string",
            "bank_code": "BankCode"
          },
          "transactions": [
            {
              "transaction_id": "string",
              "date": {
                "seconds": "int64",
                "nanos": "int32"
              },
              "type": "TransactionType",
              "status": "TransactionStatus",
              "amount": {
                "cur": "CurrencyISO4217",
                "num": "string"
              },
              "descriptor": "string",
              "match_id": "string",
              "from": {
                "account_id": "string",
                "type": "AccountType",
                "owner_ids": "[]string",
                "account_number": "string",
                "nick": "string",
                "balance": {
                  "cur": "CurrencyISO4217",
                  "num": "string"
                },
                "holder_name": "string",
                "bank_code": "BankCode"
              },
              "to": {
                "account_id": "string",
                "type": "AccountType",
                "owner_ids": "[]string",
                "account_number": "string",
                "nick": "string",
                "balance": {
                  "cur": "CurrencyISO4217",
                  "num": "string"
                },
                "holder_name": "string",
                "bank_code": "BankCode"
              },
              "fields": {
                "name": "string",
                "memo": "string",
                "account_no": "string",
                "company": "string"
              }
            }
          ],
          "account_pdfs": "bytes"
        }
      ],
      "error": "string",
      "request": {
        "seconds": "int64",
        "nanos": "int32"
      },
      "create": {
        "seconds": "int64",
        "nanos": "int32"
      },
      "external_id": "string",
      "channel": "string",
      "country": "string",
      "is_idp": "bool",
      "sub_status": "StatementSubStatus",
      "update": {
        "seconds": "int64",
        "nanos": "int32"
      },
      "is_notification_success": "bool",
      "site_response": "string",
      "challenge": {
        "type": "ChallengeType",
        "data": "bytes"
      },
      "shortcode": "string",
      "": "map[string]bytes"
    }
  ],
  "next_page_token": "string",
  "message": "string"
}

Response codes

StatusDescription
200A successful response.
404Returned when the resource is not found.

Send TFA request

Send two factor authentication request.

curl -X POST \
	https://docs.brank.as/v1/tfa \
	-H 'Authorization: Bearer USE_YOUR_TOKEN' \
	-d '{
		"purpose": "TFAPurpose",
		"purpose_id": "string",
		"token": "string"
	}'

HTTP Request

POST https://docs.brank.as/v1/tfa

Body Parameters

NameTypeDescription
purposeTFAPurposepurpose defines what this TFA token should be used for.
purpose_idstringpurpose_id is the identifier for the object that this TFA token will be used for. For example, if purpose==BankCredentialLogin, purpose_id will be a bankcredential_id.
tokenstringtoken is the actual TFA token string.
Enums
TFAPurpose
ValueDescription
UnknownPurpose
BankCredentialLogin
FundTransferAuthentication

Responses

Response body

NameTypeDescription
statusStatusstatus defines the result of the request.
auth_statusAuthStatusauth_status defines the result of the request.
status_msgstringstatus_msg is the bank status message.
Enums
Status

Status is an enum type defining whether an operation succeeded.

ValueDescription
UNKNOWN_Status
ERROR
SUCCESS
AuthStatus
ValueDescription
UNKNOWN_AuthStatus
INCOMPLETE
COMPLETE

Example:

{
  "status": "Status",
  "auth_status": "AuthStatus",
  "status_msg": "string"
}

Response codes

StatusDescription
200Request executed successfully.
404Returned when the resource is not found.
400Returned when the request body is malformatted or does not match the expected request.
401Returned when the request does not contains the user’s credentials.
403Returned when the user does not have permission to access the resource.
500Returned when an unexpected error occured on the server side.