List of exportable columns

This is an exhaustive list of all the exportable columns you can use with the COLUMNS parameter.
You have to respect the syntax with or without spaces.
Also be careful to only use parameters which are relevant for a payment method.
For example, when requesting a standard payment, you shoudn’t provide columns AUTHORIZEDBY or CAPTUREDBY.
These parameters should be use for CAPTURE or AUTHORIZATION operations. Requesting a non-compatible parameter for a given payment method will result in empty columns in the export.

  • 3DSECI string (1)

    Electronic Commerce Indicator.

    Example: 5

  • 3DSECURE no, yes

    The transaction has been processed with 3-D Secure.

    Example: true

  • 3DSECUREAUTHENTICATIONSTATUS y, n, u, a, c, r, empty

    Authentication status:

    y = authentication successful
    n = not authenticated
    u = unavailable
    a = attempted
    c = cardholder challenge required
    r = rejected
    empty = no 3-D Secure

    Example: y

  • 3DSECUREFEE string (1-64)

    Additional fee per transaction on arbitration for submission to a strong authentication challenge.

    Example:

  • 3DSECURESIGNATURESTATUS y, n

    Signature status.

    Example: y

  • 3DSGLOBALSTATUS ok, not_enrolled, unavailable, not_required

    Global status.

    Example: ok

  • 3DSLIABILITYSHIFT ‘yes’, ‘no’

    3D-Secure Liability Shift.

    Example:

  • ADDITIONAL DATA string

    Bank response additional data from authorization request.

    Example:

  • ALIAS string(1-40)

    Identifier of a previously processed payment method.

    Example: A1-fc5bafe3-8c12-4314-95c7-2e15ec3220e0

  • ALIASMODE oneclick, subscription

    Indicates the ALIAS usage mode:
    oneclick indicates a one click or an online transaction;
    subscription indicates an offline transaction.

    Example: oneclick

  • AMOUNT decimal

    Amount of the transaction (the point is used as a decimal separator).

    Example: 1000

  • AMOUNT IN BILLING CURRENCY integer

    Transaction amount in the billing currency.

    Example:

  • ARN string

    Acquirer Reference Number.

    Example:

  • AUTHENTICATION string

    Cardholder authentication mechanism.

    Example: 3DSECURE

  • AUTHORIZATION NUMBER string

    Authorization number (POS only).

    Example:

  • AVS CODE string(1)

    The Address Verification System result code. See the Address Verification System result codes section.

    Example: A

  • AVS MESSAGE string(1, 255)

    The Address Verification System result message. See the Address Verification System result codes section.

    Example: A

  • BANK COLLECTION NUMBER string(1-50)

    Bank collection number (POS only).

    Example:

  • BILLING ADDRESS string(1-50)

    The billing address as specified by the merchant in the original payment request.

    Example:

  • BILLING COUNTRY string(2)

    The billing country (ISO_3166-1_alpha-2) as specified by the merchant in the original payment request.

    Example: USA

  • BILLING CURRENCY string(3)

    Billing and payment currency.

    Example: EUR

  • BILLING FIRST NAME string(1-15)

    The first name part of the billing address as specified by the merchant in the original payment request.

    Example: John

  • BILLING LAST NAME string(1-15)

    The last name part of the billing address as specified by the merchant in the original payment request.

    Example: Doe

  • BILLING MOBILE PHONE string(1-32)

    Billing mobile phone number in international format as specified by the merchant in the original payment request.

    Example: 33111111111

  • BILLING NETWORK string(1-10)

    Billing network.

    Example:

  • BILLING PHONE string(1-32)

    Billing phone number in international format as specified by the merchant in the original payment request.

    Example: 33111111111

  • BILLING POSTAL CODE string(1-9)

    The billing postal code as specified by the merchant in the original payment request.

    Example:

  • BILLING TITLE mr, miss, mrs

    The title used for the billing address name.

    Example: mr

  • BILLING VAT FEES integer

    Billing fees on transaction (VAT fees).

    Example:

  • BILLINGFEES EX. VAT integer

    Billing fees on transaction (ex. VAT).

    Example:

  • BILLINGFEES EXCHANGE RATE integer

    Exchange rate used to calculate the fee in billing currency

    Example:

  • BILLINGFEES INCL. VAT integer

    Billing fees on transaction (incl. VAT).

    Example:

  • BRAND string

    Equipement brand (POS only).

    Example:

  • CARD PRODUCT consumer,corporate

    Card product.

    Example:

  • CARD SERVICE TYPE debit,credit,prepaid,universal

    Card service type

    Example:

  • CARD SUBTYPE string

    Card type (advanced).

    Example:

  • CARD3DSECUREENROLLED y, n, u

    Card 3-D Secure enrollment status.

    Example: y

  • CARDBANK string

    Cardholder’s bank.

    Example: BNPPARIBAS

  • CARDCODE string(12-19)

    Last 4 digits of holder’s card.

    Example: XXXXXXXXXXXX4444

  • CARDCODE 6X4 string(12-19)

    First six and last 4 digits of holder’s card.

    Example: 111122XXXXXX4444

  • CARDCOUNTRY string(2)

    The country code (format ISO_3166-1_alpha-2).

    Example: US

  • CARDFULLNAME string(1-255)

    The holder’s full name (as described on the payment method).

    Example: JOHN SNOW

  • CARDTYPE string

    The payment method type.

    Example: VISA

  • CARDVALIDITYDATE date(MM-YY)

    Card expiry date.

    Example: 12-17

  • CB2A int(2)

    Bank response code from authorization request.

    Example:

  • CHARGEBACK CODE string(1-255)

    Chargeback reason code.

    Example:

  • CHARGEBACK REASON string(1-255)

    Chargeback reason details.

    Example:

  • CHARGEBACKDATE date(YYYY-MM-DD)

    Chargeback date.

    Example: 2017-05-25

  • CHARGEBACKSTATUS first chargeback, representment, first chargeback cancellation, second chargeback, second chargeback cancellation, retrieval request, pre-compliance issuer, pre-compliance acquirer, compliance, pre-arbitration, arbitration

    Chargeback type.

    Example: chargeback

  • CHARGED_DATE date(YYY-MM-DD)

    Date of commission payment to the merchant.

    Example: 2017-05-25

  • CHARGED_REFERENCE string(0-45)

    Reference of the transfer in which commissions were taken for the transaction.

    Example: 20170926.150.18168221583972500

  • CLIENTADDRESS string(1-510)

    The user’s address.

    Example: 285 Fulton Street.

  • CLIENTDOB date(YYYY-MM-DD)

    The user’s date of birth.

    Example: 1982-06-20

  • CLIENTEMAIL email(5-255)

    The user’s email.

    Example: john.snow@example.com

  • CLIENTIDENT string(1-255)

    Unique identifier of the user in your application (e.g. a login or a primary key).

    Example: john.snow

  • CLIENTIP ipv4

    The user’s public IP address.

    Example: 10.1.1.1

  • CLIENTREFERRER string(1-255)

    The user’s HTTP referrer URL.

    Example: https://your_shop.com/order?id=1234

  • CLIENT_IDENTIFIER string

    Client export identifier (Export Sevices only).

    Example: Dalenys IDENTIFIER

  • CLIENT_INTERNAL_ID string(1-125)

    Unique Client identifier.

    Example:

  • COLLECTION DATE datetime(yyyy-MM-dd HH:mm:ss)

    Settlement date.

    Example: 2017-05-01

  • COLLECTION NUMBER integer

    Settlement number (only for POS transactions)

    Example:

  • CSF float

    Fees charged by the card schemes (Visa or Mastercard).

    Example:

  • CURRENCY string(3)

    Currency code (ISO 4217 format).

    Example: EUR

  • CVVRESPONSECODE M, N, P, S, U, X, Y, Z

    Authentication status:

    M = CVV2/CVC2 Matches
    N = CVV2/CVC2 does not Match
    P = Not processed
    S = The CVV2 should be on the card but the merchant indicates it is not.
    U = CVV2/CVC2 Unavailable – issuer does not support this parameter
    X = No information (only for JCB)
    Y = CVC1 Incorrect
    Z = Information not provided

    Example: M

  • DATE date(YYYY-MM)

    Required and mutually exclusive with STARTDATE and ENDDATE. Month or day of data to be exported, formatted YYYY-MM ou YYYY-MM-DD.

    Example: 2016-12

  • DESCRIPTION string(1-510)

    A short description of the operation, can be used to trigger fraud actions. Don’t hesitate to ask your Payment Manager for some advice on this topic.

    Example: Knows nothing

  • DESCRIPTOR string

    The transaction label sent to the bank network. The transaction will display with this label on the user’s bank statement.

    Example: myshop.com

  • EPT RANK int(3)

    Payment terminal rank (only for POS transactions).

    Example:

  • EXECCODE string(4)

    The operation result code. (See the complete list of execution code)

    Example: 0000

  • EXTRADATA string(1-255)

    Free field (Dalenys will send you back the content of the EXTRADATA you specified ahead).

    Example: referrer=myshop.com;order=premium

  • FINANCIALSTATE being processed,collected,paid, charged

    Transaction financial state (‘Being processed’; ‘Collected’ ; ‘Paid’; ‘Charged’).

    Example: `paid`

  • FORM ATTEMPT 1,2,3,4

    Form attempt number

    Example: some of stuff

  • IDENTIFIER string(1-32)

    Your processing account technical identifier.

    Example: YOUR_IDENTIFIER

  • INITIALSCHEMETRANSACTIONID string(1-55)

    Scheme transaction ID of the first transaction used to store the card information.

    Example: 11034331402111290210

  • INTERCHANGE FEE integer

    Interchange fee.

    Example:

  • IP COUNTRY ipv4

    holder’s IP country.

    Example: 120.1.1.1

  • ITP string(12)

    Terminal application identification at point of acceptance (POS only)

    Example: 552904001002

  • LANGUAGE fr, en, de, es, it, nl, zh, ru, pt, cs

    Configure the hosted form display language.

    Example: en

  • LAST NOTIFICATION CONTENT string(1-45)

    Last notification content.

    Example: OK

  • LAST NOTIFICATION HTTP CODE sent,succeeded,pending,failure

    Last notification http code.

    Example: `sent`

  • LAST NOTIFICATION RESULT sent,succeeded,pending,failure

    Last notification result.

    Example: `sent`

  • LOCATION string(1-35)

    Equipment location: open field that can be modified on the POS inventory page of your dashboard (POS only).

    Example:

  • MERCHANT COUNTRY string(2)

    Merchant’s country used in the interchange calculation.

    Example: FR

  • MESSAGE string(no length limit)

    The operation result description linked to EXECCODE.

    Example: The transaction has been accepted

  • METADATA string(1-255)

    Additional transactional data. Contact your account manager for more informations.

    Example: @METADATA-MYWEBSITE

  • MID integer

    Merchant Identification.

    Example:

  • MODEL int(3)

    Equipment model (POS only).

    Example:

  • NATURE arbitration, chargeback, chargeback reversal, pre-arbitration, rdr, rdr reversal, retrieval request, representment, representment reversal

    Nature of the operation. Same as OPERATIONTYPE until a specific event from the chargeback workflow occurs. In this case, indicates ‘retrieval request’, ‘chargeback’ or ‘representment’.

    Example: `chargeback`

  • NFC y,n

    Contactless transaction (POS only)(‘yes’; ‘no’).

    Example: y

  • OPERATIONTYPE authorization, payment, capture, refund, credit, void

    The action you want to process.

    Example: payment

  • OPPOTOTA_ENTRY_DATE datetime(yyyy-MM-dd HH:mm:ss)

    Oppotota entry date.

    Example: 2017-05-01

  • OPPOTOTA_REASON lost,stolen,did not reach cardholder,counterfeit,misuse

    Oppotota reason.

    Example:

  • ORDERID string(1-40)

    Unique ID associated to an order in the merchant’s database (as specified in your initial POST request)

    Example: 1234

  • PAYMENT METHOD TYPE CARDS, INTERNATIONAL_CARDS, AMEX, PAYPAL, BCMC, IDEAL, GIROPAY, SOFORT, KLARNA_INVOICE, PAYSAFECARD, TITRE_RESTAURANT, PRZELEWY, SDD, MULTIBANCO, FACILYPAY, APPLEPAY, COFIDIS, POSTFINANCE, CASINO

    Indicates the type of the payment method used for the transaction.

    Example: PAYPAL

  • PAYMENT OPTION facilypay-3x, facilypay-3xsansfrais, facilypay-4x, facilypay-4xsansfrais

    Facily Pay payment options.

    Example: facilypay-3x

  • POS TERMINAL TYPE ept,mpos, kiosk

    POS terminal type (‘EPT’; ‘mPOS’; ‘Kiosk’)(POS only)

    Example: `ept`

  • PP_ADDRESS STATUS none, confirmed, unconfirmed

    Status of street address on file with PayPal.

    Example: `confirmed`

  • PP_PAYER ID STATUS string(13)

    ID of Paypal payer’s account

    Example: A12345BCD6789

  • PP_PAYER STATUS none, canceled-reversal, completed, denied, expired, failed, in-progress, partially-refunded, pending, refunded, reversed, processed, voided, completed-funds-held

    The status of the payment.

    Example: completed

  • PP_PROTECTION ELIGIBILITY eligible, partiallyeligible, ineligible

    The kind of seller protection in force for the transaction.

    Example: eligible

  • PP_PROTECTION ELIGIBILITY TYPE itemnotreceivedeligible, unauthorizedpaymenteligible, ineligible

    The kind of seller protection in force for the transaction.

    Example: itemnotreceivedeligible

  • PP_SHIP TO CITY string(40 Bytes)

    Shipping city.

    Example: New York City

  • PP_SHIP TO COUNTRY CODE string(2)

    Country code.

    Example: NY

  • PP_SHIP TO NAME string(1-32)

    Holder’s shipping last name.

    Example: John Doe

  • PP_SHIP TO STREET string(1-100)

    Shipping street address.

    Example: Fulton St

  • PP_SHIP TO ZIP CODE string(1-20)

    U.S. ZIP code or other country-specific postal code.

    Example: 10007

  • PP_TRANSACTION ID string(20 max)

    Unique transaction ID of the payment.

    Example: a1B2c3D4e5F6g7H8

  • REASON string(1-125)

    Rule Description.

    Example:

  • REF ARCH string(1-12)

    Retrieval reference number.

    Example:

  • REFUND TRANSFER REFERENCE string(1-32)

    Refund transfer reference.

    Example: A1123456

  • REFUND TRANSFER STATUS pending,failed,succeeded

    Refund transfer status (‘Pending’, ‘Failed’, ‘Succeeded’).

    Example: `pending`

  • REFUNDED string

    Refunded transaction ID, if OPERATIONTYPE=’refund’.

    Example: A1234

  • REFUNDEDBY string(0-n)

    Refund transaction IDs (separated by commas ,) if this transaction is refunded.

    Example:

  • REFUNDTYPE refund,cancel

    Refund type (‘refund’;’cancel’).

    Example: `refund`

  • RETRY string(no length limit)

    Payment schedule information (retry number - number of retries).

    Example: 1-4 | 1-3 | 2-3

  • RULE APPLIED string(1-125)

    Rule applied by fraud rule engine.

    Example:

  • RULE IDS string(1-255)

    Rule IDs applied by fraud rule engine.

    Example:

  • SALE REFERENCE IDENTIFICATION string(1-12)

    A reference sent by the cash desk. Corresponds to the Order ID in the Dalenys Dashboard. (POS only)

    Example: CO25953200

  • SALE REFERENCE NUMBER string(1-12)

    ID of the Transaction generated by the cash desk. Corresponds to the Sale ID in the Dalenys Dashboard. (POS only)

    Example: DZ20855100

  • SCHEDULE string(no length limit)

    Payment schedule information (installment number - number of instalments).

    Example: 1-4 | 1-3 | 2-3

  • SCHEMETRANSACTIONID string(1-55)

    Scheme transaction ID, retrieved in response to the authorization request.

    Example: 11034331402111290210

  • SERIAL NUMBER string(12)

    Payment terminal serial number (POS only).

    Example:

  • SHIP TO ADDRESS string(1-50)

    The shipping address.

    Example: 55 rue de la liberté

  • SHIP TO COUNTRY string(2)

    The shipping country (ISO_3166-1_alpha-2 format).

    Example: US

  • SHIP TO FIRST NAME string(1-15)

    Holder’s first name in the shipping address.

    Example: John

  • SHIP TO LAST NAME string(1-30)

    Holder’s last name in the shipping address.

    Example: Doe

  • SHIP TO MOBILE PHONE string(1-32)

    Shipping mobile phone number in international format.

    Example: 33111111111

  • SHIP TO PHONE string(1-32)

    Shipping phone number in international format.

    Example: 33111111111

  • SHIP TO POSTAL CODE string(1-9)

    The shipping postal code.

    Example: 10007

  • SHIP TO TITLE mr, miss, mrs

    Holder’s title in the shipping address..

    Example: mr

  • SHORTNAME string (1-64)

    POI Short Name (POS only).

    Example: store1

  • SIRET string

    SIRET number.

    Example: 012345678912345

  • SUBMERCHANT COUNTRY string

    Country of the Submerchant

    Example: FR

  • SUBMERCHANT DOING BUSINESS AS string

    Commercial name of Submerchant

    Example: Example Startup

  • SUBMERCHANT MCC string

    Merchant Category Code of the Submerchant

    Example: 5945

  • SUBMERCHANT NAME string

    Legal name of Submerchant

    Example: Example Startup Inc.

  • SUBMERCHANT ONLINE CHANNEL boolean

    Indicates the Submerchant’s e-commerce activity (true/false)

    Example: true

  • SUBMERCHANT POS CHANNEL boolean

    Indicates the Submerchan’s proximity activity (true/false)

    Example: false

  • SUBMERCHANT STATUS string

    Indicates the status of the Submerchant (Enabled / Disabled)

    Example: ENABLED

  • SUBMERCHANT WEBSITE string

    Website of the Submerchant

    Example: https://www.test.com

  • SUBMERCHANTS EXTERNAL IDS string(32)

    Sub-merchants external ID as received in the transaction request.

    Example:

  • TAGS string(no max length)

    Tags set by the Dalenys’s rule engine

    Example: POTENTIAL FRAUD=Volume&TO BE CHECKED=Custom 1

  • TERMINAL ID ans8

    Card acceptor terminal identification (field 41 CB2A) (POS only)

    Example: 04884583

  • TRADE NAME

    Trade name.

    Example:

  • TRANSACTION EXPIRATION DATE datetime(yyyy-MM-dd HH:mm:ss)

    Transaction expiration date.

    Example:

  • TRANSACTION ORIGIN DIRECTLINK, FORM, EXTRANET, BATCH, REDIRECTION, POS, DIRECT_SUBMIT, VAD_INTERNAL, PRT_RECEIVER, MULTIBANCO_MEPS, HOSTED_FIELD, POS_INTERNATIONAL

    Indicates the origin of the transaction.

    Example: POS

  • TRANSACTIONID string(1-32)

    Unique Dalenys transaction ID. Make sure to store this ID in your database.

    Example: A1123456

  • TRANSFER REFERENCE string(1-45)

    Transfer reference.

    Example:

  • UDV string(10)

    Dalenys merchant account.

    Example:

  • VERSION 3.0

    The API protocol version.

    Example: 3.0

  • VOIDED string(1-40)

    Voided transaction ID.

    Example: A1234

  • VOIDEDBY string(1-40)

    Void transaction ID.

    Example: A1234

  • VOIDTYPE authorization,capture,payment,refund,credit

    Void type.

    Example: capture