Transaction Types

The following section reviews the transaction processes and provides implementation guidelines and examples to process, format, and send transactions using XML API, and


  • All code samples provided in this document are examples and should not be used for live transactions.

  • Only the minimum required fields, as well as recommended fields are shown in this section. Additional fields may be passed at transaction run time. Required fields are based on the merchant account configuration within Converge. For best possible transaction rates, Elavon recommends passing as much information as possible. For an extensive list of available HTML/XML value pair input fields, refer to the Supported Transaction Input Fields section.

  • Converge allows you to set up custom defined fields and define them as required or optional. You need to consider the following when using any custom defined fields:

  • Only 25 fields can be set up for any given terminal, each field can be up to 999 alphanumeric characters long, and no special characters should be used.

  • You are not allowed to pass any sensitive data, including but not limited to PAN data such as full card number, expiration date, social security numbers, track data, or CID/CVV2 data from a credit card into a custom field.

  • The integrated application should not store or print the track data, CVV2, CVC2, or CID data from the back or front of credit cards.

  • Use XML API for XML formatted request in the following transactions:

  • Credit card transactions

  • Debit card transactions

  • EBT transactions

  • Gift card transactions

  • Loyalty card transactions

  • Electronic check transactions

  • PINless debit transactions

  • Cash tender transactions

  • Card manager transactions

  • End of Day transactions

  • Account Admin transactions:

  • Use for key value pairs formatted request in Batch Import transactions.

  • Use for XML formatted request in Account Admin transactions.