The table below lists the fields that can be configured and displayed in the Payment/Transaction Search Grid of the Merchant Portal. Merchants can select which fields should appear in the search results based on their operational and reporting needs.

Depending on the payment method, available transaction data or merchant configuration, some fields may not contain values for certain transactions and may therefore appear empty in the search results.


FieldDescriptionSource/parameterPayment method
Creation dateDate and time when the transaction was created in the system.

Paygate generated

ALL
Merchant idUnique identifier assigned to the merchant.midALL
Payment idUnique identifier of the payment record.PayIDALL
Merchant reference numberReference number provided by the merchant for tracking the transaction.TransIDALL
Reference numberInternal reference number associated with the transaction.refnrALL
Transaction Reference Number

Reference number provided by the merchant for tracking the transaction (xaction).

For example if they provide individual reference number for several partial captures.

refnrALL
Payment methodMethod used to perform the payment (e.g., card, bank transfer).Name of the payment method in the format "Category - Type/Brand"ALL
CurrencyCurrency used for the transaction.CurrencyALL
AuthorisedAmount that was approved during the authorization process.amountALL
CapturedAmount successfully captured from the customer.amountFor the payment method that involves Authorization and Capture
CreditedAmount refunded or credited back to the customer.amountALL (if refund exists)
StatusCurrent processing status of the transaction.successful, Failed, PendingALL
Card numberMasked card number used for the payment.CCNr or card.JSONCard
Card brandBrand of the card used (e.g., Visa, Mastercard).card.JSON or Input on the card formCard
Approval codeAuthorization code returned by the card issuer.Code returned from external processor on authorization requestFilled only if an approval or authorization or similar code is present in the response from external system. Mostly present for card payments. 
3DSVerVersion of the 3-D Secure authentication used for the transaction.3d Secure data from ACS serverCard
Account holderName of the bank account holder for bank-based payments.AccOwnerSEPA
AcquirerBank or payment processor handling the transaction.Merchant configurationCard
API-CustomCustom data provided through the payment API integration.CustomALL
BICBank Identifier Code of the customer’s bank.BICSEPA
CaptureIndicates whether the transaction has been captured.

Paygate flag (if capture transaction exists)

For the payment method that involves Authorization and Capture
Card acceptor ID/VUIdentifier of the merchant accepting the card payment from acquirerMerchant configuration - contract number Card
Card BINFirst six digits of the card identifying the issuing bank.

Card Info extracted by Paygate

Card
Card countryCountry where the card was issued.

Card Info extracted by Paygate

Card
Card expiryExpiration date of the card used in the transaction.card.JSONCard
Card holderName of the card holder.card.JSONCard
Card issuerBank or financial institution that issued the card.

Card Info extracted by Paygate

Card
ChannelChannel through which the payment was initiated (e.g., online, phone order).

Channel

ALL
CityCity of the customer billing address.

address.json

ALL
CoF-InitialIndicates whether the transaction is the initial card on file transaction.

credentialOnFile

Card (only for card on file transactions)
CoF-TypeType of credential on file transaction (e.g., recurring or unscheduled).

credentialOnFile

Card (only for card on file transactions)
Created byUser who created the Moto transaction in Merchant PortalMerchant portal usernameMoto transaction
Customer idUnique identifier assigned to the customer.CustomerIdALL
CustomField[n]Optional custom field for merchant-specific information. Merchants can customize up to 14 special fields (called CustomField1 to CustomField14) 

CustomField[n]

ALL
ECI valueIndicator describing the authentication level for the card transaction.
Refer: ECI-Codes
3DS authentication parameter from ACS serverCard (3D Secure)
E-mail addressEmail address associated with the payment.emailALL
First nameCustomer’s first name.Payment specific parameter firstname or if provided with Billing or shipping information JSON objectALL
IBANInternational Bank Account Number used for bank payments.ibanSEPA
Invoice idIdentifier of the related invoice.InvoiceIDIf parameter InvoiceID is present in the payment request.
IP addressIP address from which the transaction was initiated.ipAddressif present in the request
ivr directIndicates whether the payment was initiated through an IVR system.-only for PBL via Paytweak
LanguageLanguage selected during the payment process.languageALL
Last nameCustomer’s last name.Payment specific parameter lastname or if provided with Billing or shipping information JSON object
Last updateDate and time when the transaction was last updated.

Paygate generated


Mandate idIdentifier for the SEPA direct debit authorization.MandateIDSEPA
Order descriptionDescription of the order or purchase.DescriptionALL
Order idIdentifier of the related order.OrderIDALL
Partial paymentIndicates whether the payment is part of a split or partial payment.-
Pseudo card numberTokenized or masked version of the card number used for secure processing.PCNrCard
Pseudo IBANMasked or alternative IBAN used for secure processing.PBANSEPA
Requested servicePayment service requested during processing.Merchant configuration
Scheme reference idReference identifier assigned by the card scheme.schemeReferenceIDCard
StreetStreet address of the customer billing address.

address.json

ALL
Terminal numberIdentifier of the terminal used to process the payment.Merchant configurationCard
TxTypeType of transaction (e.g., authorization, capture, refund).xactionALL
Zip codePostal code of the billing address.

address.json

ALL


Application Button

The button at the bottom allows you to jump to the corresponding page within the application. You must be logged in to jump to the corresponding page within the application.