Transactions
Read what happened on a card and correct it — transaction history, pending provisions, reversals and slip receipts.
doPaymentTransaction
Performs a credit card payment transaction. Returns transaction identifiers (UTID, RRN, AuthCode), response codes, and success status.
Part of:
-
Journey 01 · Launching a new card product — step 6, Post the first transaction
-
Journey 02 · Managing a card product — step 1, Post and quote payments
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
doPaymentTransaction › Request Body
transactionSourceChannel the payment comes from, forwarded as ChannelID to online. Prefer the three-digit channel code; see the Channels page.
transactionTypePayment kind online expects — INV, HGS, REL, SGK, TAX (and related institution types such as RINV).
amountPayment amount. Must be greater than zero.
tranDateBusiness date of the payment.
A date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
shadowCardNumberThe platform's card reference the payment is posted against.
institutionCodeInstitution / biller code the payment is for.
referenceNumberCaller reference for the payment; used for reconciliation and reverse.
feeAmountFee when calculated by the caller (IsFeeCalculatedExternally).
bsmvAmountBSMV portion of the fee when calculated by the caller.
descriptionFree-text description stored with the online payment.
doPaymentTransaction › Responses
Success
isSuccessWhether the operation did what it was asked to. A false here arrives with HTTP 200, so it has to be read rather than inferred from the status.
uTIDThe unique transaction identifier the platform gives a transaction, and the handle every later operation on it takes. Returned by the transaction listings.
authCodeThe authorisation code the issuer returned when the transaction was approved. Six characters, from the scheme.
rrnThe retrieval reference number — the card scheme's handle for the transaction, and what a bank quotes when asking the scheme about it.
responseCodeThe downstream system's own result code, passed through. 00 and 0 are success; anything else is its refusal, and responseReasonCode or the description says which.
responseReasonCodeWhy the downstream system answered as it did, where it narrows the response code.
responseCodeDescriptionThe description of responseCode, carried alongside it for display. It is not a key: match on the code.
reversePaymentTransaction
Reverses a payment transaction using the provided shadow card number, UTID, reference number, and authorization code.
Part of:
- Journey 02 · Managing a card product — step 4, Reversals
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
reversePaymentTransaction › Request Body
uTIDUTID returned by the original doPaymentTransaction.
referenceNumberSame reference number as the original payment.
shadowCardNumberCard the original payment was posted on.
authCodeAuthorisation code from the original payment response.
amountPresent on the contract but not forwarded to online by the digital-channels layer; reverse is keyed by UTID / reference / auth.
reversePaymentTransaction › Responses
Success
isSuccessWhether the operation did what it was asked to. A false here arrives with HTTP 200, so it has to be read rather than inferred from the status.
uTIDThe unique transaction identifier the platform gives a transaction, and the handle every later operation on it takes. Returned by the transaction listings.
authCodeThe authorisation code the issuer returned when the transaction was approved. Six characters, from the scheme.
responseCodeThe downstream system's own result code, passed through. 00 and 0 are success; anything else is its refusal, and responseReasonCode or the description says which.
responseCodeDescriptionThe description of responseCode, carried alongside it for display. It is not a key: match on the code.
responseReasonCodeWhy the downstream system answered as it did, where it narrows the response code.
responseReasonCodeDescriptionThe description of responseReasonCode, carried alongside it for display. It is not a key: match on the code.
doPaymentFeeInquiry
Inquires the payment fee for a credit card transaction. Returns fee, BSMV, total commission, and transaction identifiers like UTID, RRN, and authorization code.
Part of:
-
Journey 01 · Launching a new card product — step 6, Post the first transaction
-
Journey 02 · Managing a card product — step 1, Post and quote payments
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
doPaymentFeeInquiry › Request Body
transactionSourceChannel of the would-be payment; see the Channels page.
transactionTypeSame transaction type codes as doPaymentTransaction.
amountPrincipal amount the fee is calculated against.
tranDateBusiness date used for the fee calculation.
A date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
shadowCardNumberThe card the fee is calculated for.
institutionCodeInstitution / biller code.
referenceNumberCaller reference for the inquiry.
descriptionOptional description passed through to online.
doPaymentFeeInquiry › Responses
Success
feeAmountThe fee charged on the transaction.
bsmvAmountThe BSMV levy on the transaction.
totalCommissionAmountuTIDThe unique transaction identifier the platform gives a transaction, and the handle every later operation on it takes. Returned by the transaction listings.
authCodeThe authorisation code the issuer returned when the transaction was approved. Six characters, from the scheme.
rrnThe retrieval reference number — the card scheme's handle for the transaction, and what a bank quotes when asking the scheme about it.
responseCodeThe downstream system's own result code, passed through. 00 and 0 are success; anything else is its refusal, and responseReasonCode or the description says which.
responseReasonCodeWhy the downstream system answered as it did, where it narrows the response code.
responseCodeDescriptionThe description of responseCode, carried alongside it for display. It is not a key: match on the code.
getCustomerTransactionDetail
Retrieves detailed information about a customer transaction based on the provided UTID (Unique Transaction ID). The method fetches the transaction and associated credit card information, calculates installment limits, and adjusts them if the transaction occurs in an emergency city, applying the appropriate multiplier. The response includes transaction amount, date, description, and the calculated installment counts and limits.
Part of:
- Journey 02 · Managing a card product — step 3, History and detail
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCustomerTransactionDetail › Request Body
utidThe unique transaction identifier the platform gives a transaction, and the handle every later operation on it takes. Returned by the transaction listings.
getCustomerTransactionDetail › Responses
Success
getCardIntermTransactionInfo
Retrieves all intermediate transactions for a card, including detailed transaction info, rewards, installment info, MCC summaries, statement summary, and digital slip details. Supports pagination and optional inclusion of waiting installments.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCardIntermTransactionInfo › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
addWaitingInstallmentsWhether instalments not yet billed are included.
pageNumberWhich page of results to return, counting from 1.
rowCountHow many rows a page holds.
getCardIntermTransactionInfo › Responses
Success
lastStatementTotalDebtlastStatementUsedPointtotalCurrentPointstatementDateA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
nextStatementDateA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
remaingStatementDebtWhat is left of the statement's debt.
nextgetPendingProvisionList
Retrieves a list of pending provisions (pending transactions) for a given ShadowCardNumber. The service aggregates transaction details including amounts, currency, transaction date and description, earned rewards, installment eligibility, MCC and product info, transaction type, merchant details, and authorization/response info. Transactions are enriched with MCC definitions, card product info, and transaction code matrices. Special handling is applied for refunded transactions and certain channels (e.g., GetirFinans). Returns the mapped list of CreditCardPendingTransactionItem objects for integration purposes.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getPendingProvisionList › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
getPendingProvisionList › Responses
Success
getCreditCardTransactionAll
Retrieves all credit card transaction data using ShadowCardNumber or MainCardRefNumber. Validates card information, fetches current period transactions, pending provisions, installment transactions, and next period installments. Calculates total amounts, debts, estimated statement debt, remaining statement debt, and returns detailed transaction, installment, provision, and statement-related information.
Part of:
- Journey 02 · Managing a card product — step 3, History and detail
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCreditCardTransactionAll › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
mainCardRefNumberThe card reference of the main card. On a supplementary card this is the card it hangs from; on a main card it is the card's own reference.
beginDateA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
endDateA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
onlySuccessFlagWhether to return only the transactions that succeeded.
getCreditCardTransactionAll › Responses
Success
getCreditCardCurrentTransactionList
Retrieves the current period credit card transaction list using ShadowCardNumber or MainCardRefNumber. Fetches all transactions for the current statement period, separates installment and non-installment transactions, and enriches transaction data with transaction code descriptions and channel descriptions. Returns summary financial information such as current debt, estimated statement debt, remaining statement debt, total amount, and detailed transaction lists including amounts, dates, merchant info, rewards, installment details, and channel information.
Part of:
-
Journey 01 · Launching a new card product — step 6, Post the first transaction
-
Journey 02 · Managing a card product — step 3, History and detail
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getCreditCardCurrentTransactionList › Request Body
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
mainCardRefNumberThe card reference of the main card. On a supplementary card this is the card it hangs from; on a main card it is the card's own reference.
getCreditCardCurrentTransactionList › Responses
Success
getTransactionAll
Retrieves all credit card transactions for a given card, including current period transactions, next period installments, and reward transactions. The service validates the card, fetches current and upcoming installments, filters reward transactions, and maps them into response models. The response includes CreditCardCurrentPeriodTransactions (current period transactions and pending provisions) and CreditCardNextPeriodInstallments (installments for the next period), with details on amounts, dates, descriptions, rewards, installments, and card product attributes.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getTransactionAll › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
mainCardRefNumberThe card reference of the main card. On a supplementary card this is the card it hangs from; on a main card it is the card's own reference.
beginDateA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
endDateA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
onlySuccessFlagWhether to return only the transactions that succeeded.
getTransactionAll › Responses
Success
getPendingProvisionListNew
Retrieves a list of pending provisions (pending transactions) for a given ShadowCardNumber. The service aggregates transaction details including amounts, currency, transaction date and description, earned rewards, installment eligibility, MCC and product info, transaction type, merchant details, and authorization/response info. Transactions are enriched with MCC definitions, card product info, and transaction code matrices. Special handling is applied for refunded transactions and certain channels (e.g., GetirFinans). Returns the mapped list of CreditCardPendingTransactionItem objects for integration purposes.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getPendingProvisionListNew › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
getPendingProvisionListNew › Responses
Success
getDigitalSlipReceipt
Retrieves the digital slip (transaction receipt) for a given UTID (Unique Transaction ID) and channel. The method returns detailed transaction information including card numbers (masked and shadow), transaction amount and currency, merchant details, authorization and response codes, terminal and transaction identifiers, ICC data, and transaction status.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
getDigitalSlipReceipt › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
utidThe unique transaction identifier the platform gives a transaction, and the handle every later operation on it takes. Returned by the transaction listings.
getDigitalSlipReceipt › Responses
Success
utidThe unique transaction identifier the platform gives a transaction, and the handle every later operation on it takes. Returned by the transaction listings.
refUtidThe transaction this one refers to — the original, for a reversal or a correction.
trnCodeMatrixIdWhich row of the transaction-code matrix this transaction was classified by.
shadowCardNumberThe platform's own handle for a card, and the identifier most operations take. It is returned by every operation that creates a card and by the card listings; a caller does not compose one.
cardRefNumberThe card reference, which identifies one issued card including its renewals. Returned by the create and listing operations alongside the shadow number.
maskedCardNumberThe card number with its middle digits masked, as the platform stores it. It is a display form, not a key: operations take the shadow number.
trnAmountThe amount of the transaction, in its own currency.
trnCurrencyCodeThe currency the transaction was made in.
responseCodeThe downstream system's own result code, passed through. 00 and 0 are success; anything else is its refusal, and responseReasonCode or the description says which.
trnDatetimeA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
trnStatusWhere the transaction has got to.
stanThe system trace audit number — the scheme's sequence number for the message, unique within a day and a terminal.
rrnThe retrieval reference number — the card scheme's handle for the transaction, and what a bank quotes when asking the scheme about it.
authorizationNumberThe authorisation code the issuer returned when the transaction was approved. Six characters, from the scheme.
terminalNumberThe terminal the transaction was made at.
merchantNumberThe merchant's number with the acquirer.
merchantNameThe merchant's name as it reached the platform from the scheme.
panEntryModeHow the card was read at the terminal — chip, stripe, contactless, keyed, or stored on file. The scheme's own code.
iccData84iccData9f26cardSeqNumberWhich chip on the card was used, where a customer holds more than one card on the same number.
merchantAddressThe merchant's address as it reached the platform.