Skip to content
English
Customer portal
eComCharge Blog
  • There are no suggestions because the search field is empty.

Get the list of processed transactions

Request

The requests must:

Send a POST request to {YOUR DWH URL}/api/v2/transactions/list with the following parameters:

Warning

Pay attention that the maximum number of transactions in the response is limited to 1000 (if options.limit is not specified in the request, the default limit is 100). If the number of transactions meeting the request criteria is more than the limit specified in the request, send another request using parameter values from the pagination object in the response. More information here.

Parameter Type Description Partial match
response_parameters GraphQL query A string of transaction parameters that need to be sent in the response. Format example: "response_parameters": "query {transactions {uid status description}}"

For possible values, see the table below.		 N/A
options object   N/A
limit integer The number of transactions in the response.

Minimum allowed value: 1.
Maximum allowed value: 1000.
Default value is 100.		 N/A
time_zone string The PSP timezone as defined here, for example, Europe/Vilnius.

Default value is Etc/UTC. Make sure to send this parameter if your timezone is different from UTC+00:00 so that the time values in the response are converted into your timezone.		 N/A
filter object   N/A
date_from * required string A start date of the reporting period in ISO 8601 format — YYYY-MM-DDThh:mm:ss±hh:mm, for example, 2024-01-24T23:13:39+02:00. The timezone in the parameter value must match the one specified in options.time_zone.

The date must occur within 90 days before the value of the date_to parameter.

Must equal next_date value from the response to the previous request if you send multiple requests for the same date range and the results don't fit into the limit specified in the first request.		 N/A
uid_from * conditionally required string Required if you send multiple requests for the same date range and the results don't fit into the limit specified in the first request.

Must equal next_uid value from the response to the previous request.		 N/A
date_to * required string An end date of the reporting period iin ISO 8601 format — YYYY-MM-DDThh:mm:ss±hh:mm, for example, 2024-01-24T23:13:39+02:00. The timezone in the parameter value must match the one specified in options.time_zone.

The date must occur within 90 days after the value of the date_from parameter.		 N/A
date_type string A date type.

Possible values:
created_at is a date when a transaction is created (set by default);
paid_at is a date when a transaction is paid;
updated_at is a date when a transaction is updated.		 N/A
merchant_id string A string of merchant IDs. Submit as a string with a single or multiple values separated with commas. N/A
shop_id string A string of shop IDs. Submit as a string with a single or multiple values separated with commas. N/A
uid string (36) Transaction identifier

 +
description string (1024) Transaction description. +
type string A string of transaction types for which the data needs to be returned in the response. Submit as a string with a single or multiple values separated with commas.

Possible values:
authorization,
payment,
tokenization,
payout,
capture,
void,
refund,
credit,
chargeback.		 N/A
status string A string of transaction statuses for which the data needs to be returned in the response. Submit as a string with a single or multiple values separated with commas.

Possible values:
successful,
failed,
incomplete,
error,
pending.		 N/A
amount string Transaction amount. Submit as a string of one or more big integer values, separated with commas. N/A
currency string Transaction currency. Submit as a string with a single or multiple values separated with commas. The values must be in the ISO-4217 format, for example, USD. N/A
test boolean By default, false. If true, the data on test transactions will be returned. N/A
code string (7) Transaction result code. N/A
recurring_type string Submit as a string with a single or multiple values separated with commas.

Possible recurring types:
recurring,
initial,
null.		 N/A
fraud string (20) Fraud check result.

Possible values:
reject - the transaction was rejected, for example, if the card's BIN is in the blacklist,
review - the transaction is under review of the PSP.		 N/A
tracking_id string (500) A transaction identifier in the merchant's system. +
gateway_id string Identifier(s) of payment gateway(s) enabled for the merchant's shop. Submit as a string with a single or multiple integer values separated with commas. N/A
gateway_type string Name(s) of payment gateway(s) enabled for the merchant's shop. Submit as a string with a single or multiple values separated with commas. N/A
gateway_agent_id string Identifier(s) of merchant's agent account(s). Submit as a string with a single or multiple integer values separated with commas. N/A
shop_business_category_id integer Business category assigned to the merchant's shop. N/A
provider_raw_rrn string (64) A retrieval reference number. A transaction ID issued by a card processing network. +
provider_raw_ref_id string (510) Transaction identifier in the provider's system. +
customer_id string Customer's ID in the PSP system. N/A
customer_ip string (255) The customer's IP address upon making a payment. N/A
customer_full_name string (255) The customer's full name (first name, last name and patronymic). +
customer_phone string (100) The customer's phone number. +
customer_email string (255) The customer's email address. +
method_type string A payment method.

Possible values:
credit_card stands for card payment methods;
alternative stands for non-card-based payment methods.		 N/A
method_alternative_account string (255) Payment method attribute, for example, an account in the alternative payment method system. N/A
credit_card_product string (255) A card brand or product. N/A
credit_card_first_1 string (1) The first digit of the credit card number. N/A
credit_card_bin string (6) 6-digit bank identification number. N/A
credit_card_bin_8 string (8) 8-digit bank identification number. N/A
credit_card_last_4 string (8) The last 4 digits of the card number. N/A
credit_card_holder string (70) A cardholder's name. +
credit_card_brand string (60) A card brand. N/A
credit_card_sub_brand string (60) A card sub-brand. N/A
credit_card_stamp string (128) A card hash. It is constant even if the expiration date or card holder are changed. N/A
credit_card_issuer_country string (2) A country of the bank that issued the card in the ISO 3166-1 alpha-2 format. N/A
recipient_customer_id string Recipient's ID in the PSP system. N/A
recipient_customer_ip string (255) The recipient's IP address upon making a payment. N/A
recipient_customer_full_name string (255) The recipient's full name (first name, last name and patronymic). +
recipient_customer_email string (255) The recipient's email address. +
recipient_customer_phone string (100) The recipient's phone number. +
recipient_credit_card_product string (255) A brand or product of the recipient's card. N/A
recipient_credit_card_first_1 string (1) The first 1 digit of the recipient's card. N/A
recipient_credit_card_bin string (6) 6-digit bank identification number of the recipient's card. N/A
recipient_credit_card_bin_8 string (8) 8-digit bank identification number of the recipient's card. N/A
recipient_credit_card_last_4 string (8) The last 4 digits of the recipient's card number. N/A
recipient_credit_card_holder string (70) A holder's name of the recipient's card. +
recipient_credit_card_brand string (60) A brand of the recipient's card. N/A
recipient_credit_card_sub_brand string (60) A sub-brand of the recipient's card. N/A
recipient_credit_card_stamp string (128) The hash of the recipient's card. It is constant even if the expiration date or card holder are changed. N/A
recipient_credit_card_issuer_country string (2) The country of the bank that issued the recipient's card in the ISO 3166-1 alpha-2 format.  

Request example

{
  "options": {
    "limit": 5,
    "time_zone": "Europe/Vilnius"
  },
  "filter": {
    "date_from": "2024-01-01T06:30:20+02:00",
    "date_to": "2024-01-03T06:33:18+02:00",
    "date_type": "created_at",
    "currency": "EUR,USD"
  },
  "response_parameters": "query { transactions { uid status description amount currency type tracking_id created_at paid_at settled_at psp_settled_at updated_at manually_corrected_at expired_at closed_at message friendly_message code language test parent_uid reason converted_currency converted_amount recurring_type subscription_id product_id fraud merchant{enabled id name company_name bank_id legal_address email postal_code country city} shop{enabled id name company_name business_category_id contact_phone url contact_email legal_address mailing_address postal_code country city} provider_raw{auth_code bank_code rrn ref_id message dynamic_billing_descriptor amount currency} gateway{id type note agent_id vendor connection_type} links{receipt_url redirect_url return_url notification_url} three_d_secure_verification{status message acs_url pa_req md pa_res_url eci pa_status xid cavv cavv_algorithm fail_reason method_process_url creq} customer{id ip first_name last_name middle_name full_name gender birth_date phone email address country city zip state device_id taxpayer_id}  method{credit_card{product first_1 bin bin_8 last_4 holder exp_month exp_year brand sub_brand stamp token token_provider issuer_country issuer_bank}} recipient{customer{id ip first_name last_name middle_name full_name gender birth_date phone email address country city zip state device_id}} method {type alternative_account alternative_type alternative_payment_info}  smart_routing_verification avs_cvc_verification provider_response}}"
}

Pagination

The number of transactions in the response is limited to 1000 items (if options.limit isn't specified in the request, the default limit for the number of transactions in the response is 100). If there are more than 1000 transactions that fit the date range and filtering criteria, send another request and specify the value of pagination.next_date from the previous response as the value of filter.date_from parameter. And use the value of pagination.next_uid from the response as the value of filter.uid_from in the subsequent request. It's essential to use both filter.date_from and filter.uid_from parameters in the subsequent requests and use the same value in the date_type parameter.

Request example for subsequent transactions 

{
    "options": { 
            "limit": 5,
            "time_zone": "Europe/Vilnius"

    },
    "filter":  {
            "date_from": "2024-01-01T07:30:24.978000+02:00",
            "date_to": "2024-01-03T06:33:18+02:00",
            "date_type": "created_at",
            "currency": "EUR,USD"           
    },
    "response_parameters": " query { transactions { uid status description amount currency type tracking_id created_at paid_at settled_at psp_settled_at updated_at manually_corrected_at expired_at closed_at message friendly_message code language test parent_uid reason converted_currency converted_amount recurring_type subscription_id product_id fraud merchant{enabled id name company_name bank_id legal_address email postal_code country city} shop{enabled id name company_name business_category_id contact_phone url contact_email legal_address mailing_address postal_code country city} provider_raw{auth_code bank_code rrn ref_id message dynamic_billing_descriptor amount currency} gateway{id type note agent_id vendor connection_type} links{receipt_url redirect_url return_url notification_url} three_d_secure_verification{status message acs_url pa_req md pa_res_url eci pa_status xid cavv cavv_algorithm fail_reason method_process_url creq} customer{id ip first_name last_name middle_name full_name gender birth_date phone email address country city zip state device_id taxpayer_id}  method{credit_card{product first_1 bin bin_8 last_4 holder exp_month exp_year brand sub_brand stamp token token_provider issuer_country issuer_bank}} recipient{customer{id ip first_name last_name middle_name full_name gender birth_date phone email address country city zip state device_id}} method {type alternative_account alternative_type alternative_payment_info}  smart_routing_verification avs_cvc_verification provider_response}}"
}

Possible values of the response_parametersparameter in the request

Below is the list of the possible values of response_parameters in the request. See the format in the example above. If these values are specified in the request, the corresponding parameters will be included in the response. Parameters in bold are default parameters that will be sent in the response even if response_parameters are not specified.

Parameter Description
transactions  
uid * required Unique transaction identifier in the PSP system.
status Transaction status.

Possible values:
successful,
failed,
incomplete,
error,
pending.
description Transaction description.
amount Transaction amount.
currency Transaction currency.
type Transaction type.
tracking_id A transaction identifier in the merchant's system.
created_at Date and time when a transaction was created.
paid_at Date and time of the payment.
settled_at Date and time of the transaction settlement between the acquirer and the merchant.
psp_settled_at Date and time of the transaction settlement between the PSP and the merchant.
updated_at Date and time when the transaction was updated.
manually_corrected_at Date and time when the transaction was manually updated.
expired_at Date and time when the transaction expired.
сlosed_at Date and time when the transaction was closed.
message A message for the merchant with the request result.
friendly_message A message for the customer with the request result.
code Transaction result code.
language Language of the checkout page.
test If true, the transaction is a test one.
parent_uid Identifier of the parent transaction in the PSP system.
reason A note why a refund was made.
converted_currency A currency to which a transaction amount was converted.
converted_amount Transaction amount after conversion.
recurring_type Possible recurring types:
recurring,
initial,
null
subscription_id Subscription identifier.
product_id Subscription plan identifier.
fraud Result of the fraud check.
merchant  
enabled If true, the merchant is active.
id Merchant's identifier in the PSP system.
name Merchant's name.
company_name The name of the merchant's company.
bank_id The identifier of the merchant's bank.
legal_address The address of the merchant's company.
email The email of the merchant's company.
postal_code The postal code of the merchant's company.
country The country where the merchant's company is registered.
city The city where the merchant's company is registered.
shop  
enabled If true, the shop entity is active.
id The shop's identifier.
name The shop's name.
company_name The name of the shop's company.
business_category_id The identifier of the shop's business category.
contact_phone The shop's phone number.
url The website of the shop.
contact_email The contact email of the shop.
legal_address The address where the shop is registered.
mailing_address The mailing address of the shop.
postal_code The postal code of the shop's legal address.
country The country where the shop is registered.
city The city where the shop is registered.
provider_raw  
auth_code Authorization code of the provider.
bank_code Transaction result code in the provider's system.
rrn A retrieval reference number assigned to a transaction.
ref_id Transaction identifier in the provider's system.
message Transaction result message in the provider's system.
dynamic_billing_descriptor The description of the transaction result in the provider's system.
amount Transaction amount in the provider's system.
currency Transaction currency in the provider's system.
gateway  
id Gateway id in the PSP system.
type Gateway name in the PSP system.
note Gateway description.
agent_id Identifier of the agent assigned to the shop.
vendor Gateway type.

Possible values:
gateway for card integrations,
beyag for alternative integrations.
connection_type Gateway connection type. The value of the Connection type field in the gateway settings. As a rule, it contains keywords that are used for data grouping in the accounting reports.
links  
receipt_url Link to the receipt in PDF.
redirect_url A URL of the page to finalize the transaction.
return_url The link where the customer is redirected once they return from 3-D Secure verification.
notification_url The link where the webhook notifications are sent.
three_d_secure_verification  
status 3-D Secure authentication status.
message Message about 3-D Secure authentication status.
acs_url URL to the Access Control Server form (ACS form) where the password received from the bank needs to be entered.
pa_req Payer authentication request, encoded.
md Unique transaction identifier, used to link the merchant's server and the issuing bank's server.
pa_res_url URL where the issuing bank’s server sends a response to the payment authentication request.
eci Electronic Commerce Indicator. Provides information regarding merchant protection level against chargebacks requests by the cardholders or their banks.
pa_status Status of payment authentication in the 3-D Secure protocol.
xid 3-D Secure transaction unique identification code.
cavv Cardholder Authentication Verification Value (present only if the cardholder has been successfully authenticated).
cavv_algorithm CAVV algorithm.
fail_reason The message with the reason for 3-D Secure authentication failure.
method_process_url URL for additional check based on the browser data.
creq 3-D Secure authentication request, encoded.
customer  
id Customer's identifier in the payment service system.
ip The customer's IP address upon making a payment.
first_name The customer's first name.
last_name The customer's last name.
middle_name The customer's patronymic.
full_name The customer's full name (first name, last name and patronymic).
gender The customer's gender.
birth_date The customer's birth date.
phone The customer's phone number.
email The customer's email address.
address The customer's address.
country The customer's country.
city The customer's city.
zip The customer's postal code.
state The state of the customer.
device_id The identifier of the device used for the payment.
taxpayer_id Taxpayer identifier assigned to the customer.
method  
credit_card  
product A card brand or product.
first_1 The first 1 digit of the credit card.
bin 6-digit bank identification number.
bin_8 8-digit bank identification number.
last_4 The last 4 digits of the card number.
holder A cardholder's name.
exp_month Expiration month of the credit card.
exp_year Expiration year of the credit card.
brand The brand of the credit card.
sub_brand The sub-brand of the credit card.
stamp The card hash. It is constant even if the expiration date or card holder are changed.
token A card token that was received in the transaction response when the card was charged for the first time.
token_provider Token's provider, for example, apple_pay.
issuer_country A country of the bank that issued the card in the ISO 3166-1 alpha-2 format.
issuer_bank The bank that issued the card.
recipient  
customer  
id Customer's identifier in the PSP system.
ip The customer's IP address upon making a payment.
first_name The customer's first name.
last_name The customer's last name.
middle_name The customer's patronymic.
full_name The customer's full name (first name, last name and patronymic)
gender The customer's gender.
birth_date The customer's birth date.
phone The customer's phone number.
email The customer's email address.
address The customer's address.
country The customer's country.
city The customer's city.
zip The customer's postal code.
state The state of the customer's address.
device_id The identifier of the device used for the payment.
method  
type Alternative payment method name.
alternative_account Payment method attribute specific to the APM.
alternative_type Payment method attribute specific to the APM.
alternative_ payment_info Additional payment info specific to the APM.
smart_routing_verification Object with Smart Routing verification results.
avs-cvc_verification Object with AVS/CVC verification results.
provider_response Object with additional information from the provider response.

Response

The response contains the following parameters:

Parameter Type Description
data object A section of transaction report parameters.
pagination object  
date_from string date_from value from the request.
date_to string date_to value from the request.
date_type string date_type value from the request.
has_next_page boolean The parameter indicating that there are more transactions that meet the request parameters than those sent in the response.

Possible values:
true, if there are more transactions that meet the request parameters;
false, if all the transactions that meet the request parameters are sent in the response.
next_date string A date of the next transaction that meets the request parameters, but is not sent in the response. The date is of the type submitted in the date_type request parameter.

To get more transactions that are not included in the response, send the received date value as a value of the date_from parameter in the request.
uid_from string The uid of the first transaction in the response body.
uid_to string The uid of the last transaction in the response body.
next_uid string The uid of the next transaction the meets the request parameter but is not included in the response because of the limit. Use the value of next_uid parameter in your next request to get the next transactions in the specified date range with the specified parameters that didn't fit into the limit.
transactions array An array of transactions that meet the request parameters. Each element represents a transaction object with mandatory parameters and those parameters listed in the response_parameters of the request.
updated_at string A date when a transaction was updated.
smart_routing_verification object Object with the results of the transaction check by Smart Routing service.

 

The parameters of the smart_routing_verification object

Parameter Type Description
status string The status of the transaction check by Smart Routing service. Possible values:

successful - check passed;
failed - the transaction didn't pass the check.
data object Object with the detailed information of the transaction check results.
status string The transaction check status.

Possible values:

rejected - the transaction was rejected by the rule with the action reject or the transaction parameters are included in the black list,
passed - in all other cases.
object string The ID of the gateway to which the transaction was sent for processing; null if all gateways were excluded by the check.
object_name string The name of the gateway that processed the transaction.
object_flows array An array of flows of object type against which the transaction was checked. Each object contains the following parameters:

name - flow name;

system - rule type (true if it's a system rule, otherwise, false);

skipped - flow check status (true if the check against the flow was skipped, otherwise, false);

rules - an array of rules within this flow.
rules array An array of objects where each object corresponds to a particular rule in the flow.
alias string The rule's name.
state string The result of the rule check.
description string The rule description.
error_message string The error message.
error_code string The error code.

Possible values:

precondition_failed - precondition isn't matched;
rule_inactive - the rule is inactive;
rule_unprocessable - the rule is not ready to be used, for example, it has been just created. This error happens in rare cases;
allowed_objects_mismatch - the gateway selected by the rule wasn't available, for example, it was excluded by another rule;
data_mismatch - aggregation rule error, if the transaction doesn't meet the aggregation requirements, it doesn't participate in the aggregation, for example, in calculating the sum of the transactions meeting a particular condition;
not_enough_data - missing data for checking the transaction against the conditions.
object_defined_via string The method used to select the gateway for the transaction.

Possible values:

allowed objects - as a result of the Smart Routing checks, no particular gateway was selected, the transaction was sent to one of the available gateways that was selected either randomly or sequentially based on the Smart Routing account settings;
rule - object was selected as a result of the rule.
action_rules object Object with the detailed information on the transaction check against the rules of action type.
{account_name} object Object with the detailed information about the rules that are active for the account. The parameter name includes the identifier of the account, on the level of which the rule was created. The name of the parameters of PSP, merchant and shop level follow the formats PSP_{psp_id}, Merchant_{merchant_id}, Shop_{shop_id} respectively.
{flow_name} object Object with the detailed information about the flow to which the rule belongs.
{rule_name} object The status of the transaction check against the rule. Parameter name matches the rule name.

Possible values:

passed - the check was performed, the transaction didn't match the rule conditions;
skipped - the check against the rule wasn't performed, for example, the parameter from the rule condition has null value, or the transaction parameters are in the whitelist;
allow - the check against the rule was performed, as a result the transaction was approved for further checks;
skip 3DS - as a result of the check, the 3D-Secure verification isn't required for the transaction;
notify - as a result of the rule; the notification was sent;
review - as a result of the check the transaction was marked as suspicious and the corresponding email was sent to the anti-fraud email provided in the shop settings;
reject - as a result of the check the transaction was rejected.
matched_actions object Object with the actions that were performed for the transaction.
{action name} array An array of rules that resulted in the action. Each rule in the array is an object that includes the rule name (alias), rule description (description), the corresponding account name (account) and, only for notify action, the % value, upon reaching which the notification was sent (breached_threshold).
wb_lists object Object with the white and black lists that were applied to the transaction. If the transaction parameters didn't match the ones in the lists, the value of the corresponding parameter will be not_matched. Otherwise, matched.

Response example

{
    "data": {
        "transactions": [
            {
                "amount": 3608,
                "created_at": "2024-01-01T07:30:20.762000+02:00",
                "currency": "USD",
                "merchant_id": 366,
                "paid_at": "2024-01-01T07:30:20.964000+02:00",
                "shop_id": 343,
                "status": "successful",
                "type": "authorization",
                "uid": "95813fc8-0488-4fda-893a-d03130456d2f"
            },
            {
                "amount": 879,
                "created_at": "2024-01-01T07:30:21.423000+02:00",
                "currency": "USD",
                "merchant_id": 366,
                "paid_at": "2024-01-01T07:30:21.617000+02:00",
                "shop_id": 343,
                "status": "successful",
                "type": "capture",
                "uid": "3c0c6f09-b6d6-419b-940e-7fe1b98a6ac6"
            },
            {
                "amount": 1979,
                "created_at": "2024-01-01T07:30:22.040000+02:00",
                "currency": "USD",
                "merchant_id": 366,
                "paid_at": "2024-01-01T07:30:22.255000+02:00",
                "shop_id": 343,
                "status": "successful",
                "type": "authorization",
                "uid": "794734e6-3932-47d0-99b1-c640730e7293"
            },
            {
                "amount": 4639,
                "created_at": "2024-01-01T07:30:22.841000+02:00",
                "currency": "USD",
                "merchant_id": 366,
                "paid_at": "2024-01-01T07:30:23.047000+02:00",
                "shop_id": 343,
                "status": "successful",
                "type": "payment",
                "uid": "1cd98e2e-7ed4-44f6-a4d3-42211e42ce3c"
            },
            {
                "amount": 1257,
                "created_at": "2024-01-01T07:30:24.186000+02:00",
                "currency": "EUR",
                "merchant_id": 366,
                "paid_at": "2024-01-01T07:30:24.444000+02:00",
                "shop_id": 343,
                "status": "successful",
                "type": "authorization",
                "uid": "9084b001-6a55-4eed-b09c-0467ee6941b9"
            }
        ],
        "pagination": {
            "date_type": "created_at",
            "has_next_page": true,
            "uid_from": "95813fc8-0488-4fda-893a-d03130456d2f",
            "date_from": "2024-01-01T07:30:20.762000+02:00",
            "date_to": "2024-01-01T07:30:24.186000+02:00",
            "next_date": "2024-01-01T07:30:24.978000+02:00",
            "next_uid": "f1cb7674-e043-450b-a60c-3765f088a401",
            "uid_to": "9084b001-6a55-4eed-b09c-0467ee6941b9"
        }
    }
}

Response example with smart_routing_verification object 

{
  "data": {
    "transactions": [
      {
        "created_at": "2024-01-01T05:30:20.762000+02:00",
        "smart_routing_verification": {
          "data": {
            "status": "passed",
            "object": "3405",
            "object_name": "gw_3405",
            "object_flows": [
              {
                "name": "Test_object_flow",
                "system": false,
                "skipped": false,
                "rules": [
                  {
                    "alias": "123456",
                    "state": "skipped",
                    "description": "1234567",
                    "error_message": "Rule is inactive",
                    "error_code": "rule_inactive"
                  },
                  {
                    "alias": "Shop_rule",
                    "state": "skipped",
                    "description": "7564",
                    "error_message": "Rule is inactive",
                    "error_code": "rule_inactive"
                  },
                  {
                    "alias": "rule_1 gw_1_33201, gw_2_33202, gw_3_33203",
                    "state": "skipped",
                    "description": "description",
                    "error_message": "Rule is inactive",
                    "error_code": "rule_inactive"
                  },
                  {
                    "alias": "Test object rule",
                    "state": "skipped",
                    "description": "321",
                    "error_message": "No intersection between 'objects' and 'allowable_return_values'",
                    "error_code": "allowed_objects_missmatch"
                  },
                  {
                    "alias": "Test object rule 2",
                    "state": "matched",
                    "description": "Notifications",
                    "use_only_these_objects": true
                  }
                ]
              }
            ],
            "object_defined_via": "rule",
            "action_rules": {
              "Psp_1_ООО beGateway1": {
                "Calibri": {
                  "Test1234567": "skipped"
                },
                "psp rule, reject EUR txns": {
                  "psp rule": "skipped"
                }
              }
            },
            "matched_actions": {
              "skipped": [
                {
                  "alias": "psp rule, reject EUR txns",
                  "description": "psp rule",
                  "account": "Psp_1_ООО beGateway1"
                },
                {
                  "alias": "Calibri",
                  "description": "Test1234567",
                  "account": "Psp_1_ООО beGateway1"
                }
              ]
            },
            "wb_lists": {
              "merchant_black_list": "not_matched",
              "merchant_white_list": "not_matched",
              "psp_black_list": "not_matched",
              "psp_white_list": "not_matched",
              "shop_black_list": "not_matched",
              "shop_white_list": "not_matched"
            }
          }
        }
      },
      {
        "created_at": "2024-01-01T05:30:21.423000+02:00",
        "smart_routing_verification": {
          "data": {
            "status": "passed",
            "object": "456",
            "object_name": "gw_456",
            "action_rules": {
              "Psp_1_Demo PSP": {
                "country flow": {
                  "choose country": "passed"
                }
              }
            },
            "matched_actions": {
              "passed": [
                {
                  "account": "Psp_1_Demo PSP",
                  "alias": "country flow",
                  "description": "choose country"
                }
              ]
            },
            "object_defined_via": "allowed objects",
            "object_flows": []
          },
          "status": "successful"
        }
      }
    ],
    "pagination": {
        "date_from": "2024-01-02T05:30:19.720000+02:00",
        "date_to": "2024-01-02T05:30:20.621000+02:00",
        "date_type": "created_at",
        "has_next_page": true,
        "uid_from": "36d87fc6-8a51-4d8e-a573-0c8ee0764b28",
        "next_date": "2024-01-02T05:30:21.373000+00:00",
        "next_uid": "f53009ee-0781-4237-9351-21b4eeeecd93",
        "uid_to": "ddadaae1-812e-42c6-a551-114ca178e91f"
    }
  }
}