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

Appendix 2: List of system fields

When integrated with the beGateway payment processing system, the Smart Routing service analyzes and processes the following fields:

Table: System fields used in the Smart Routing service 

 

SR parameter name

 

Used in aggregation conditions

 

Description

 

Display name

 
1

bank_token_provider

Bank, provider of the card token.

Bank token provider

2

bin_country

+

A country of the card issuing bank derived from the card number sent in requests in the ISO 3166-1 alpha-2 format.

Card issuer’s country code

3

card_bin

An identification number of the card issuing bank (a card BIN) derived from the card number sent in requests.

Card BIN (8)

4

card_bin_6

6-digit bank identification number (BIN). The first 6 digits of the card number.

Card BIN (6)

5

card_mask

+

The card mask, for example, 123456XXXX1234.

Card mask

6

card_pan

The card PAN.

Card PAN

7

card_product

The product code of the credit/debit card. For example, MDS(Debit Mastercard Card).

Card product code

8

cvv_present

Refers to the CVC or CVV parameter of a card sent in requests.

CVV in request

9

gateway_id

+

A gateway ID set by the system.

Gateway ID

10

force_3ds

+

Attribute of mandatory 3DS verification. Overrides the value of skip_3ds attribute.

Force 3DS option

11

merchant_country

+

A country where the merchant’s legal entity is registered, as indicated in the system.

Merchant’s country code

12

object_note

+

A gateway agreement note, as stated in the gateway settings.

Gateway note

13

pa_res_status

A 3D Secure version 1.0 check result.

3DS PaRes status

14

pm_account_number

+

A parameter for the alternative payment method transactions. In most cases, stands for the identifier of the customer’s account.

Transaction account number

15

pm_brand

+

A card brand sent in requests or derived from the card number sent in requests.

Payment method brand

16

pm_holder

+

A cardholder’s name.

Payment method holder

17

pm_issuer

+

A card issuing bank derived from the card number sent in requests.

Payment method issuer

18

pm_last_4

+

The last 4 digits of the card number.

Last 4 digits of card PAN

19

pm_stamp

+

A unique card hash derived from the card number sent in requests.

Payment method stamp

20

pm_sub_brand

+

A sub-brand of the card.

Payment method sub-brand

21

recipient_card_bin

An identification number of the recipient’s card issuing bank (a card BIN) derived from the card number sent in requests.

Recipient’s card BIN

22

recipient_card_pan

PAN of the recipient’s card.

Recipient’s card PAN

23

recipient_pm_holder

+

The holder of the recipient’s card/account.

Recipient’s payment method holder

24

recipient_pm_stamp

+

A unique card hash derived from the recipient’s card number sent in requests.

Recipient’s payment method stamp

25

referer

+

URI of the resource that sent the transaction request. Typically, the URI of the webpage where the payment widget is embedded and from which the transaction was initiated.

Referer URI

26

sc_authorization_failed_count

Count of non-successful authorization transactions per card over the period of up to 360 days.

Count of failed authorizations (SC)

27

sc_authorization_successful_count

Count of successful authorization transactions per card over the period of up to 360 days.

Count of successful authorizations (SC)

28

sc_capture_failed_count

Count of non-successful capture transactions per card over the period of up to 360 days.

Count of failed captures (SC)

29

sc_capture_successful_count

Count of successful capture transactions per card over the period of up to 360 days.

Count of successful captures (SC)

30

sc_chargeback_failed_count

Count of non-successful chargeback transactions per card over the period of up to 360 days.

Count of failed chargebacks (SC)

31

sc_chargeback_successful_count

Count of successful chargeback transactions per card over the period of up to 360 days.

Count of successful chargebacks (SC)

32

sc_p2p_sender_failed_count

Count of non-successful sent p2p (p2p_sender) transactions per card over the period of up to 360 days.

Count of failed P2P transactions (SC)

33

sc_p2p_sender_successful_count

Count of successful sent p2p (p2p_sender) transactions per card over the period of up to 360 days.

Count of successful P2P transactions (SC)

34

sc_payment_failed_count

Count of non-successful payment transactions per card over the period of up to 360 days.

Count of failed payments (SC)

35

sc_payment_successful_count

Count of successful payment transactions per card over the period of up to 360 days.

Count of successful payments (SC)

36

sc_payout_failed_count

Count of non-successful payout transactions per card over the period of up to 360 days.

Count of failed payouts (SC)

37

sc_payout_successful_count

Count of successful payout transactions per card over the period of up to 360 days.

Count of successful payouts (SC)

38

sc_refund_failed_count

Count of non-successful refund transactions per card over the period of up to 360 days.

Count of failed refunds (SC)

39

sc_refund_successful_count

Count of successful refund transactions per card over the period of up to 360 days.

Count of successful refunds (SC)

40

sc_void_failed_count

Count of non-successful void transactions per card over the period of up to 360 days.

Count of failed voids (SC)

41

sc_void_successful_count

Count of successful void transactions per card over the period of up to 360 days.

Count of successful voids (SC)

42

skip_3ds

+

Attribute of skipping 3DS verification. Overridden by the value of force_3ds parameter.

Skip 3DS option

43

token_provider

+

Service token provider (for example, apple_pay)

Service token provider

44

tracking_id

+

Transaction identifier in the merchant’s system.

Tracking ID

45

txn_amount

+

Transaction amount.

Transaction amount

46

txn_bank_code

+

Transaction result code provided by the bank.

Transaction bank code

47

txn_billing_address

+

The billing address of the customer.

Customer’s billing address

48

txn_billing_address_country

The code of the customer’s billing address country.

Customer’s billing country code

49

txn_converted_amount

+

Transaction amount after the conversion into the conversion currency.

Converted amount

50

txn_conversion_currency

+

Conversion currency for the transaction.

Conversion currency

51

txn_customer_name

+

The first and last names of the customer.

Customer’s first and last name

52

txn_currency

+

Transaction currency.

Transaction currency

53

txn_device_id

+

The customer’s device ID.

Customer’s device ID

54

txn_email

+

The customer’s email specified in the transaction.

Customer’s email

55

txn_hour

The hours in which the transaction parameters were sent to Smart Routing for verification.

Transaction processing hour

56

txn_ip

+

The customer’s IP address.

Customer’s IP address

57

txn_ip_country

The customer’s country according to the customer’s IP address.

Customer’s country by IP address

58

txn_phone

+

A customer’s phone number.

Customer’s phone

59

txn_recurrent

+

A parameter of a recurring transaction.

Recurring transaction

60

txn_status

+

A transaction status.

Transaction status

61

txn_type

+

A transaction type.

Transaction type

62

txn_rrn

+

Transaction identifier in the provider's system received from the 3rd party/bank.

Transaction RRN

63

txn_ref_id

+

A transaction ID of the system of the payment method provider.

Transaction reference ID

64

txn_code

+

Transaction result code in the PSP system.

Transaction processing code

65

txn_recurring_type

-

Type of recurring transaction.

Recurring type