The Batch Authorization Service (BAS) is a component of CardConnect's Secure Exchange SFTP product. BAS allows integrating clients to submit batch files for authorization processing. 

Using BAS to transmit batch files is not a drag-and-drop solution. Integrating BAS requires development work and testing.

The request file submitted to BAS will contain all required data elements within an Authorization Request to the CardPointe Gateway. BAS collects the supplied data and submits all requests on behalf of the client. A response file is returned, containing data from the associated Authorization Response.

This details within this article are broken down into the following sections:

Client Onboarding Checklist

  1. Obtain the CardConnect pgp public key. Clients must encrypt all request files using this key.
  2. Send your client pgp public key to CardConnect. CardConnect encrypts response files using your key.
  3. Obtain SFTP credentials from CardConnect. You use these to submit requests and poll for response files.
  4. Obtain your CardConnect Gateway API URL and credentials from CardConnect.

Supported Authorization Types

The Batch Authorization Service supports all data elements that the CardPointe Gateway Authorization Service supports.

Authorization TypeDetails
'capture' column set to 'N'
Authorization with Capture
'capture' column set to 'Y'
Refund without Reference
'amount' column set to a negative value
The merchant account must be configured to support this transaction type.

PGP Keys

All files that are submitted to or retrieved from Secure Exchange must be PGP encrypted. This requires two PGP key pairs: 

  • Request keypair - CardConnect holds the private key and you download the public key. You must use this key to encrypt all BAS request files before uploading them to Secure Exchange.
  • Response keypair - You hold the private key and send the public key to CardConnect. CardConnect uses your key to encrypt all BAS response files before uploading them to Secure Exchange.

Click below to download the CardConnect public PGP keys for the UAT and Prod environments: 

Note that these keys are "armored;" run the "gpg --dearmor" command to de-armor the keys.

For example:

$ gpg --dearmor < secureexhange_uat.txt > secureexchange_uat.gpg

Request File Specifications

CardConnect Tokens

The value within each record's account field must be a valid CardConnect token. This service does not handle clear-text card numbers.

If your integration does not yet support CardConnect tokens, contact integrationdelivery@cardconnect.com.

Request File Name


Sample Request File

081800000001,1000102424,VISA,9404077753845057,1299,100,Y,USD,test@test.com,name1,add1,add2,city1,,US,19020,,,,Y,"unitcost='1.00',description='desc with no comma',uom='lb'|unitcost='1.00',description='desc with,comma',uom='lb'",,,,,,,,,,,Y,,,Y
081800000001,1000102425,VISA,9404077753845057,1299,100,N,USD,,name1,add1,add2,,,,19020,111-111-11111,,,,"unitcost='1.00',description='desc with no comma',uom='lb'",,,,,,,,,,,,,,
081800000001,1000102426,VISA,9404077753845057,1299,100,N,USD,test@test.com,,add1,,city1,,US,19020,,,,,"unitcost='1.00',description='desc with no comma',uom='lb'|unitcost='1.00',description='desc with,comma',uom='lb'",,,,,,,,,,,,,,

Request Fields

Fields in bold are required. 

Fields with a # indicate these fields can be used as part of a profile. See the CardPointe Gateway API Profile description for more information. 

Field Size Type Comments
orderid 19 AN Source system order number. Populate this field with a unique value that can identify the sales order. This value will be associated with the response record.

Note the following requirements:
  • The orderid must not contain the card or payment account number.
  • The orderid must be a unique value.
merchid 12 N CardConnect Merchant ID (MID), required for all requests
amount 12 N Amount with decimal or without decimal in currency minor units (for example, USD Pennies or EUR Cents),

This value identifies the authorization type:

- Authorization request

- Account Verification request. See AVS and CVV settings to enable. Account Verification is not available for ECHK transaction types

- Refund without reference (Forced Credit). Merchants must be enabled for forced credit. When referencing an existing authorization, use Refund.
currency 3 AN Currency of merchant settlement
(USD for US dollars, CAD for Canadian Dollars, etc.)
expiry# 4 N Card Expiration in either MMYY or YYYYMMDD format, not required for ECHK.
account# 19 N

CardSecure Token - Retrieved from the Bolt API, CardSecure API, or the Hosted iFrame Tokenizer.

The token can be generated from from either credit card or ACH (banking/routing number) data. If ACH, the merchid must be a specific Profit Stars Merchant ID.

Note: To use a CardConnect profile, omit the account field and supply the profileid. See the CardPointe Gateway API Profile description for more information.

profile 1 or 16 AN Optional, Y to create an account profile upon initial authorization. Creating a profile generates a 20-digit numeric profileid / acctid (optional) value to use in authorizations when the account field is omitted. See the CardPointe Gateway API Profile description for more information.
acctid 3 N Account identifier within a profile, specifies unique token
capture 1 A Optional, Y to capture the transaction for settlement if approved.
signature 6144 AN JSON-escaped, Base64-encoded, Gzipped, BMP of signature data. If the authorization is using a token with associated signature data, then the signature from the token is used.
cvv2 4 N CVV2/CVC/CID value
name# 30 AN Account name

Optional for credit cards but required for electronic checks.
address# 30 AN Account street address (required for AVS)
city# 30 AN Account city
postal# 9 AN Account postal code, defaults to "99999". If country is "US", must be 5 or 9 digits. Otherwise any alphanumeric string is accepted.
region# 20 AN US State, Mexican State, Canadian Province
country# 2 AN Account country (2 character country code), defaults to "US."
Required for all non-US addresses.
phone# 15 AN Account phone
email# 30 AN E-Mail address of the account holder
authcode 6 AN Authorization code from original authorization (VoiceAuth). For Voice/Capture-Only, include valid authcode.
taxexempt 1 A If taxexempt is set to No for the transaction and a tax is not passed, the default configuration data is used. If taxexempt is set to Yes, the default tax rate is used.
termid 30 AN Terminal Device ID
accttype# 6 A One of PPAL, PAID, GIFT, PDEBIT, otherwise not required.
ecomind 1 A Identifies the payment origin. Options are:

- telephone or mail
- recurring
- ecommerce/Internet
invoiceid 12 AN Invoice ID, optional, defaults to orderid from authorization request
userfields 4000 Bytes
AN The userfields object, or array is a series of name-value pairs that are meaningful to the merchant. See details here.

Example of userfields value:

"{""UDF1"": ""SomeText"", ""UDF2"": ""SomeMoreText""}"

Capture Level 2 Data

If available, the Level 2 fields can be provided in the capture request and should be provided for corporate or purchase cards to qualify for improved interchange rates.

ponumber36ANCustomer purchase order number
taxamnt12NTax amount either decimal or in currency minor units (i.e. USD Pennies, MXN Centavos), taxamnt of zero indicates tax-exempt purchaser

Note: Do not send a non-zero tax amount for a tax exempt order.

Many Level 2 protocols refer to a "Customer Code" described as "an identifier the customer would recognize". CardConnect populates this field with the ponumber. If the ponumber is not provided, then the orderid from the authorization request is used. If neither the ponumber or the orderid is available, the CardConnect-assigned Retrieval Reference Number (retref) is used.

The Level 2 protocol also requires certain fields about the merchant, such as Postal Code and Tax Identification Number. These fields are filled from the configuration table created during the merchant boarding process.

Capture Level 3 Data

If available, Level 3 line item data can be sent with the capture request, particularly for any commercial or corporate payment cards. To qualify for Level 3 Interchange rates, Level 2 data (described above) must also be provided.

Level 3 data includes additional Order Level items such as freight and discount amount, as well as information from each line item of the order. These are stored as an array in the items field.

frtamnt12NTotal order freight amount, default 0
dutyamnt12NTotal order duty amount, default 0

For most industries this is the delivery date for the order

Defaults to System Date when captured
shiptozip12ANIf country is "US", must be 5 or 9 digits

Otherwise, any alphanumeric string is accepted
shipfromzip12ANSame as above
shiptocountry2AShip To Country Code, default is US
ItemsvariesArrayArray of Items

Items Field for BAS

  • The Items field must be enclosed in double quotation marks (").
  • Each item must be separated by a pipe delimiter (|).
  • Elements in each item must be a key=value pair.
  • Elements in each item must be separated by a comma (,).
  • Each value must be enclosed in single quotation marks (').
  • Values containing a single quote (') must be escaped with a backslash (\).

    For example:
    description='desc with a single quote\''
    • Values containing a comma (,) must also be enclosed in double quotation marks (").

      For example:
      "unitcost='1.00',description='desc with no comma',uom='lb'|unitcost='1.00',description='desc with,comma',uom='lb'"

      Line Item Records

      lineno4NOptional line number for each item. Line numbers do not need to be specified sequentially; however, if no lineno value is included, items are assigned sequential line numbers.
      material12ANOptional material code (also referred to as a Commodity Code) for each item.
      description26ANAn item description, required.
      upc14NOptional UPC code for each item. If upc is included, the value must not be all zeros.

      Some processors limit this value to 12 characters.
      quantity12NQuantity of the item purchased. Can be a whole amount or amount with up to three decimal places.
      uom8ANUnit of measure (for example, "each" or "ton").

      Some processors limit this value to 4 characters.
      unitcost12NOptional item cost, excluding tax as a decimal amount or in currency minor units (for example, USD Pennies or MXN Centavos formatted as 1.23 or 123 for $1.23).

      When omitted, this value is calculated as netamnt/quantity.
      netamnt12NNet total of unitcost x quantity, excluding tax and discount, as a decimal amount or in currency minor units.

      netamnt is always a positive value, even for refunds.

      Zero amounts are allowed for no-charge items, such as a manual, that are included in the order.
      taxamnt12NTax amount for each item, as a decimal amount or in currency minor units. The sum total of taxamnt for all items equals the total tax amount for the order.

      The total of netamnt + taxamnt - discamnt equals the order amount.

      taxamnt must be zero or omitted if taxexempt is N and non-zero if taxexempt is Y.
      taxexempt1true/falseIndicates whether or not the order is tax exempt.

      taxexempt should be true if:
      • The payment card BIN type is GSA (government).

        Note: All GSA orders are set to taxexempt regardless of this setting.
      • The merchant is a government agency.

        In this case, you must include taxexempt = true in the request for each order.
      taxexempt defaults to false.
      discamnt12NOptional discount amount for each item, as a decimal amount or in currency minor units.

      Response File Specifications

      BAS response files are pgp encrypted with the key that you provided to CardConnect.  
      Response files will return one Gateway response per line.

      Response File Name

      The response file name matches the corresponding request file name with the extension ".done" appended. 

      For example:


        Sample Response File

        1,DONE,,1000102424,2345676543,2.00,Approval,C ,P,543,A,00,081800000001,9404077753845057,PPS001,FNOR,A,9404077753845057
        2,DONE,,1000102425,2345676543,3.00,Approval,C ,P,543,A,00,081800000001,9404077753845057,PPS001,FNOR,A,9404077753845057
        3,ERROR,401 Un-Authorized,1000102426
        4,DONE,,1000102427,2345676543,4.00,Declined,C ,P,543,U,00,081800000001,9404077753845057,PPS063,FNOR,C,9404077753845057
        5,LOAD_ERROR,IOException reading next record: java.io.IOException: (line 2) invalid char between encapsulated token and delimiter


        Field Content Max Len Comments
        id Integer 20 BAS transaction ID
        status String
        10 Final processing status: "DONE" or "ERROR"
        message String None Details explaining "ERROR" or "LOAD_ERROR"
        orderid Order ID 19 The orderid specified in the Request file
        retref Retrieval reference number 12 CardConnect retrieval reference number from authorization response
        amount Amount 12 Authorized amount. Same as the request amount for most approvals. The amount remaining on the card for prepaid/gift cards if partial authorization is enabled. Not relevant for declines.
        resptext Response text - Text description of response
        commcard Commercial card flag 1 Y if a Corporate or Purchase Card
        cvvresp CVV response code 1 Alpha-numeric CVV response.
        batchid Batch ID 10 Automatically created and assigned unless otherwise specified
        avsresp AVS response code 2 Alpha-numeric AVS response.
        respcode Response code - Alpha-numeric response code that represents the description of the response
        merchid Merchant ID 12 Copied from request
        token (if requested) Token 19 A token that replaces the card number in capture and settlement requests if requested
        authcode Authorization code 6 Authorization Code from the Issuer
        respproc Response processor 4 Abbreviation that represents the platform and the processor for the transaction
        respstat Status 1 A - Approved
        B - Retry
        C - Declined
        account Account number 19 Copied from request, masked

        Submitting a Batch File

        You submit request files and retrieve response files using Secure Exchange, via SFTP. When you log in to Secure Exchange you have access to three directories: /request, /response, and /dlc (dead-letter channel). 

        The following procedure describes each folder's purpose:

        1. You upload an encrypted request file into the /request directory.

          BAS decrypts the file and runs authorization requests, logging each response in a new response file.
        2. You poll the server for encrypted responses files in the /response directory.
        3. If an error occurs when attempting to decrypt the pgp file, the encrypted request file is placed in the /dlc directory.

          Contact Support if you encounter this scenario.

        Viewing Batch File Transactions in CardPointe

        To view reporting details for processed batches in CardPointe do the following:

        1. Log in to CardPointe and access the merchant account.
        2. Click Reporting in the menu bar, and select the Transactions tab.
        3. Click the Front End column header and select SecureExchange to display the transactions processed using the BAS.

        See the CardPointe Web App support page for more information on using CardPointe.