Sales File Upload

ConnexPay users have the ability to upload comma-delimited sales files to create sales transactions.

Uploading a File

This capability can be accessed from the CXP Portal by navigating to Sales → Run Transactions screen and selecting the File Upload option:

  • Key the file name and location or select the Choose File button to locate and choose the file you wish to upload
  • Once the file has been located, select ‘Upload File’ to begin the upload process

File Format Specifications

The file should be in .csv format containing the following fields:

🚧

The “DeviceGuid” and the “VC_MerchantGuid“ will be provided by ConnexPay Client Success team and will be required before uploading a file.

Field Number

Name

Type

M/C/O

Description

1

DeviceGuid

STRING

Mandatory

Device's GUID provided by ConnexPay.

2

Amount

DECIMAL

Mandatory

Amount of the transaction that will be processed.
Note: this value is submitted multiple times (in different formats) within the integration to support different purposes i.e. risk analysis, merchant processing, etc.
The minimum amount is: $0.50.

3

CurrencyCode

STRING

Mandatory

3 digit currency code (i.e. USD, CAN)

4

TenderType

STRING

Optional (will default to Credit if nothing specified)

Allowed values:

Credit
*Cash

5

SequenceNumber

STRING

Mandatory

Sequence number is a unique identifier. The file upload will fail if a sequence number is used that was previously uploaded.
The maximum length is 100 alpha-numeric characters

6

OrderNumber

STRING

Optional

Transaction ID within client environment associated with the order. The value is searchable and reportable in the ConnexPay portal. This value may be sent in multiple instances of the integration for multiple purposes. Customers in the travel space often send the Record Locator/PNR in this field.

The maximum length is 20 alpha-numeric characters.

7

CustomerID

STRING

Optional

Transaction ID within client environment associated with the customer. This value acts as a secondary identifier in conjunction with OrderNumber. The value is searchable and reportable in the ConnexPay portal. This value may be sent in multiple times within the integration for multiple purposes.

The maximum length is 50 characters and is alpha-numeric.

8

ExpectedPayments

INTEGER

Mandatory

Always set to '1'. This will create one virtual card for the amount indicated.

9

StatementDescription

STRING

Optional for Credit

Include blanks for Cash

The statement description allows a client to customize the Merchant name that appears on the cardholder statement such that the cardholder recognizes the transaction on their statement.

ConnexPay recommends sending a recognizable DBA along with the PNR i.e. ABC Travel ABC123.
Note: functionality not applicable for American Express OptBlue program.

The maximum length is 25 alpha-numeric characters.

10

CardNumber

STRING

Mandatory for Credit

Include blanks for Cash

Must be 16 characters. or token (example: FfL7exC7Xe2y6624).

11

CardHolderName

STRING

Optional

Cardholder's name. Providing information in this field allows a user of the ConnexPay portal to search for a transaction using the cardholder name.

The maximum length is 100 characters

12

CVV2

INTEGER

Optional for Credit

Include blanks for Cash

The three or four digit CVV code at the back side of the credit and debit card. This value is required for all card-not-present processing environments.

13

ExpirationDate

DATE

Optional with token

Include blanks for Cash

Card's expiry date in the YYMM format.

14

Customer_FirstName

STRING

Required

First name of the customer.

Between 2 and 30 characters.

15

Customer_LastName

STRING

Required

Last name of the customer.

Between 2 and 30 characters.

16

Customer_Phone

STRING

Optional

Customer's phone number.

Phone number up to 15 characters. Numbers and plus sign (+) allowed only.

17

Customer_City

STRING

Optional

Customer's city.

Only letters allowed

18

Customer_State

STRING

Optional

Customer's short name state.

The ISO 3166-2 CA and US state or province code of a customer.

Length = 2.

19

Customer_Country

STRING

Optional

Customer's country. The ISO country code of a customer’s country.

Length = 2

20

Customer_Email

STRING

Optional

Customer's valid email address which is available in various reports.

21

Customer_Address1

STRING

Optional

Customer billing street address. It is strongly recommended to send this value in a card-not-present environment such that enhanced Address Validation (AVS) can be performed on transaction and the lowest possible interchange is received on transaction.

Note: only the street number value portion of address is used for enhanced AVS check.

Letters and Numbers

22

Customer_Address2

STRING

Optional

Customer billing address line 2. It is strongly recommended to send this value in a card-not-present environment such that Address Validation (AVS) can be performed on transaction and the lowest possible interchange is received on transaction.

Letters and Numbers

23

Customer_Zip

INTEGER

Optional

Customer billing postal code. It is strongly recommended to send this value in a card-not-present environment such that basic Address Validation (AVS) can be performed on transaction and the lowest possible interchange is received on transaction.

Between 2 and 15 alphanumeric

24

VC_MerchantGuid

STRING

Mandatory

Merchant's GUID. Application level value that indicates a virtual card is being requested for clients account. Value provided by ConnexPay.

25

VC_FirstName

STRING

Mandatory

Cardholder's first name. This is the first name placed on the virtual card provided to the travel supplier. The value is also searchable in the ConnexPay portal.

Maximum 50 characters.

26

VC_LastName

STRING

Mandatory

Cardholder's last name. This is the last name placed on the virtual card provided to the travel supplier. The value is also searchable in the ConnexPay portal.

Maximum 50 characters.

27

VC_UsageLimit

DECIMAL

Mandatory

Security Control: Maximum number of times the card may be used - for both pre-auths and standard authorizations - for security purposes the maximum allowed value is 99. All attempts greater than 99 will be declined. For all transactions authorized by ARC, airlines typically settle for each individual ticket on a PNR that is connected to the original authorization.

28

VC_AmountLimit

DECIMAL

Mandatory

Security Control: Maximum dollar amount the card can be authorized and settled; value must incorporate any overage i.e. currency conversion, taxes that travel supplier may associate with the transaction. If a travel supplier authorizes card for more than the amount limit the transaction will be decline. Any balance remaining on the card is returned to the ConnexPay client 8-10 days through Residual Margin after expiration and all pending transactions is cleared.

Between 1 and 9999999.99. must be positive and have up to 2 decimal places. So for example 1 or 1.1 or 1.11 will work, but consistently sending 2 is best practice (1.00 for example)

29

VC_ExpirationDate

DATE

Mandatory

Security Control: The last date for which a virtual card may be authorized in YYYY-MM-DD format. For airline or other prepaid transactions, ConnexPay recommends expiring the card 8-10 days after issuance - this provides enough time to pass the card to the travel supplier and their processing. For hotel transactions, ConnexPay suggests 8-10 days after check out to ensure all pending transactions are processed. This value is critical because residual margin will not be calculated until after the defined expiration date.

30

VC_TerminateDate

DATE

Optional

The terminate date is the date the virtual card will be terminated by ConnexPay’s system. TerminateDate is different than the ExpirationDate in that TerminateDate just triggers Residual Margin and ExpirationDate is the month and year that will be applied to the actual VCC. The recommendation is to set the ExpirationDate one or two years in the future and set the TerminateDate just a day or two after the VCC is expected to be processed.

31

VC_PurchaseType

STRING

Mandatory

Security Control: The industry where the virtual card will be utilized. For example, if value set to airline and the card is used at hotel, it will be declined.

Available purchase type values are:

01 for Airline.

02 for Hotel.

03 for Car Rental.

98 for No Restriction.

99 for Other.

32

VC_SupplierId

STRING

Optional

The SupplierId is used to assist with Intelligent Routing functionality.

The field accepts up to 10 alpha-numeric characters.

File Response

If there are no errors, you will see the message “Your transactions are processing, this can take several minutes depending on the size of your file.” Upon completion of the upload, you will receive an email (to the email address associated with the username that uploaded the file) informing you of the number of sales processed, the number of Sales Declined and the number of Purchases declined, as well as a total transaction count. This total should match the number of records in your file.

Virtual Card Details

There is not a response file built yet. So after the file is done processing and you receive the email navigate to Purchases, find the Sale transaction you are looking for, expand it and then click the green card detail button to get the Virtual Card details you need.

Sample .csv file

(download the file, make the appropriate modifications and save it as a .csv file (upload will only accept a .csv format).

ConnexPay Employees can find more information here.


Did this page help you?