Payment Options Inquiry
Request to retrieve the options available for processing a payment, for example, the credit cards and currencies.
You can also use this operation to perform a Rate Quote for Dynamic Currency Conversion or to calculate the applicable Surcharge for an order.
Warning! This operation must not be called directly from the browser, as it would reveal the integration password to customers.
This operation may not be needed if such values rarely change and can be hard-coded into the website handling the transaction. However, the operation is useful for populating and validating transaction fields (for example) if these values can change in real time for a business's website.
If the operation is called with no parameters, all values that could apply for all fields are returned: all of the possible currencies, all of the possible card types, and so on. Non-complex websites can use this unmodified data set for building a website's presentation and input validation.
Some websites require more complex configuration (for example, where USD and EUR currencies are supported on MasterCard and Visa, but only USD on American Express). Call the operation with parameters to restrict the returned values. If a sourceOfFunds.provided.card.prefix is passed in, only currencies applicable to the card brand identified by the prefix are returned. If an order.currency is passed in, only payment options applicable for that currency are returned.
Authentication Copied to clipboard
This operation requires authentication via one of the following methods:
- Certificate authentication.
-
Basic HTTP authentication as described at
w3.org.
Provide 'merchant.
<your gateway merchant ID>' in the userid portion and your API password in the password portion.
Request Copied to clipboard
URL Parameters Copied to clipboard
Alphanumeric + additional characters
REQUIRED
The unique identifier issued to you by your payment provider. This identifier can be up to 12 characters in length.
Data may consist of the characters 0-9, a-z, A-Z, '-', '_'
Min length: 1 Max length: 40Fields Copied to clipboard
To view the optional fields, please toggle on the "Show optional" setting.
String
A transient identifier for the request, that can be used to match the response to the request.
The value provided is not validated, does not persist in the gateway, and is returned as provided in the response to the request.
Data can consist of any characters
Additional information about the external token repository you are configured with.
These fields are MANDATORY for MerchantLink merchants and must not contain sensitive data.
String
Provide the site code required to save card details against a token.
For example: '{"siteCode":"BNE"}'.
Data can consist of any characters
Enumeration
The interface through which the transaction is submitted to the gateway.
Value must be a member of the following list. The values are case sensitive.
AUTO
The transaction was automatically generated by the gateway. For example, a Capture transaction for Auto-Capture or an order reversal transaction for risk rejected orders.
BATCH
The transaction was submitted as part of a merchant batch. Batches can either be uploaded via Batch or via Merchant Administration.
CHECKOUT_VIA_PAYMENT_LINK
The transaction was created via checkout. The payer was redirected to checkout by clicking on a payment link.
CHECKOUT_VIA_WEBSITE
The transaction was created via checkout. The payer was redirected from your website to checkout.
MERCHANT_ADMINISTRATION
The transaction was initiated in Merchant Administration.
MERCHANT_MANAGER
The transaction was initiated in Merchant Manager.
SERVICE_PROVIDER_API
The transaction was reported by an acquirer or alternate payment provider.
WEB_SERVICES_API
The transaction was submitted via Web Services API.
String
ANZ Worldline Payment Solutions might have configured your merchant profile to support several lines of business.
Each line of business can have different payment parameters, such as bank account, supported cards or such.
For example, lineOfBusiness = TICKET_SALES can have a different bank account from lineOfBusiness = MERCHANDISING. One line of business on your profile might be "null". To use that, do not provide the lineOfBusiness field.
Data can consist of any characters except space
String
A language identifier or IETF language tag to control the language of the payment interaction with the payer (e.g. en_US, es, fr-CA).
By default, the language is determined from your configuration. Supply a value for this field only if you wish to override the default behavior. If the language you specify is not supported by the gateway, the payment is displayed in the best matching language.
See Dynamic Currency Conversion for more detail.
Data must be a language identifier or IETF language tag
Information about the order associated with this transaction.
Decimal
The total amount for the order. This is the net amount plus any surcharge.
If you provide any sub-total amounts, then the sum of these amounts (order.itemAmount, order.taxAmount, order.shippingAndHandlingAmount, order.cashbackAmount, order.gratuityAmount), minus the order.discountAmount must equal the net amount.
The value of this field in the response is zero if payer funds are not transferred.
Either Amount or netAmount must be provided
Data is a string that consists of the characters 0-9 and '.' and represents a valid decimal number.
Upper case alphabetic text
The currency of the order expressed as an ISO 4217 alpha code, e.g. USD.
Data must consist of the characters A-Z
Decimal
The amount payable for the order before surcharging is applied.
If you specify a net amount the gateway will calculate the surcharge for you. Alternatively, you can specify the surcharge amount (order.surchargeAmount) yourself.
Either Amount or netAmount must be provided
Data is a string that consists of the characters 0-9 and '.' and represents a valid decimal number.
Enumeration
The payment method the payer wishes to use to pay for this order.
Value must be a member of the following list. The values are case sensitive.
BANCANET
CARD
UNION_PAY
ASCII Text
Identifier of the payment session containing values for any of the request fields to be used in this operation.
Values provided in the request will override values contained in the session.
Data consists of ASCII characters
ASCII Text
Use this field to implement optimistic locking of the session content.
Do this if you make business decisions based on data from the session and wish to ensure that the same data is being used for the request operation.
To use optimistic locking, record session.version when you make your decisions, and then pass that value in session.version when you submit your request operation to the gateway.
If session.version provided by you does not match that stored against the session, the gateway will reject the operation with error.cause=INVALID_REQUEST.
See Making Business Decisions Based on Session Content.
Data consists of ASCII characters
Information about the payment type selected by the payer for this payment and the source of the funds.
Depending on the payment type the source of the funds can be a debit or credit card, bank account, or account with a browser payment provider (such as PayPal).
For card payments the source of funds information may be represented by combining one or more of the following: explicitly provided card details, a session identifier which the gateway will use to look up the card details and/or a card token. Precedence rules will be applied in that explicitly provided card details will override session card details which will override card token details. Each of these may represent partial card details, however the combination must result in a full and complete set of card details. See Using Multiple Sources of Card Details for examples.
This holds the PAN in the case where it is encrypted by the terminal using DUKPT key exchange.
Digits
The BIN of the card.
If you provide this, the gateway will check that the decrypted PAN has these leading six digits. If the check fails, the gateway will reject the transaction.
If you do not provided this, the gateway will not perform this check.
Data is a string that consists of the characters 0-9.
String
The P2PE encryption state as determined by the terminal.
INVALID means the terminal detected some form of error in the encryption process. The gateway will decline transactions with INVALID encryption state. This field may be omitted when the value is VALID.
Data can consist of any characters
Hex
The initialization vector supplied by the terminal to seed the encryption of this payload.
Omit this value if the terminal is not using an initialization vector to seed encryption.
Data is hexadecimal encoded
Hex
REQUIRED
The DUKPT key serial number supplied by the terminal.
Data is hexadecimal encoded
Hex
REQUIRED
The DUKPT encrypted payload supplied by the terminal.
Data is hexadecimal encoded
Digits
The first 10 digits of the card number, as printed on the card.
Data is a string that consists of the characters 0-9.
Alphanumeric
Uniquely identifies a card and associated details.
Data may consist of the characters 0-9, a-z, A-Z
Enumeration
Indicates the channel through which you received authorization for the payment for this order from the payer.
For example, set this value to INTERNET if the payer initiated the payment online.
If you have an existing agreement with the payer that authorizes you to process this payment (for example, a recurring payment) then set this value to MERCHANT. You only need to provide transaction.source if you want to override the default value configured for your acquirer link.
Note:
- You can only override the default value if you have the requisite permission.
- The value you provide must match one of those configured by ANZ Worldline Payment Solutions.
- You can only set the transaction source on the initial transaction on an order. It cannot be changed on subsequent transactions.
Value must be a member of the following list. The values are case sensitive.
CALL_CENTRE
Transaction conducted via a call centre.
CARD_PRESENT
Transaction where the card is presented to the merchant.
INTERNET
Transaction conducted over the Internet.
MAIL_ORDER
Transaction received by mail.
MERCHANT
Transaction initiated by you based on an agreement with the payer. For example, a recurring payment, installment payment, or account top-up.
MOTO
Transaction received by mail or telephone.
PAYER_PRESENT
Transaction where a non-card payment method is presented to the Merchant.
TELEPHONE_ORDER
Transaction received by telephone.
VOICE_RESPONSE
Transaction conducted by a voice/DTMF recognition system.
Response Copied to clipboard
Fields Copied to clipboard
String
A transient identifier for the request, that can be used to match the response to the request.
The value provided is not validated, does not persist in the gateway, and is returned as provided in the response to the request.
Data can consist of any characters
JSON Text
Provides additional data relevant to the options available for processing a payment.
If applicable, ANZ Worldline Payment Solutions will describe how to use this data.
Data is valid Json Format
Enumeration
The interface through which the transaction is submitted to the gateway.
Value must be a member of the following list. The values are case sensitive.
AUTO
The transaction was automatically generated by the gateway. For example, a Capture transaction for Auto-Capture or an order reversal transaction for risk rejected orders.
BATCH
The transaction was submitted as part of a merchant batch. Batches can either be uploaded via Batch or via Merchant Administration.
CHECKOUT_VIA_PAYMENT_LINK
The transaction was created via checkout. The payer was redirected to checkout by clicking on a payment link.
CHECKOUT_VIA_WEBSITE
The transaction was created via checkout. The payer was redirected from your website to checkout.
MERCHANT_ADMINISTRATION
The transaction was initiated in Merchant Administration.
MERCHANT_MANAGER
The transaction was initiated in Merchant Manager.
SERVICE_PROVIDER_API
The transaction was reported by an acquirer or alternate payment provider.
WEB_SERVICES_API
The transaction was submitted via Web Services API.
Alphanumeric + additional characters
ALWAYS PROVIDED
The unique identifier issued to you by your payment provider.
Data may consist of the characters 0-9, a-z, A-Z, '-', '_'
Decimal
The total amount for the order. This is the net amount plus any surcharge.
If you provide any sub-total amounts, then the sum of these amounts (order.itemAmount, order.taxAmount, order.shippingAndHandlingAmount, order.cashbackAmount, order.gratuityAmount), minus the order.discountAmount must equal the net amount.
The value of this field in the response may be zero if payer funds are not transferred.
Data is a decimal number.
Upper case alphabetic text
The currency of the order expressed as an ISO 4217 alpha code, e.g. USD.
Data must consist of the characters A-Z
Decimal
The amount payable for the order before surcharging is applied.
If you specify a net amount the gateway will calculate the surcharge for you. Alternatively, you can specify the surcharge amount (order.surchargeAmount) yourself.
Data is a decimal number.
Decimal
A fee charged by you to cover the cost of accepting a payment method.
Data is a decimal number.
The payment method the payer wishes to use to pay for this order.
Details about supported BancaNet browser payment options.
Information on the currencies supported for this order.
Upper case alphabetic text
The list of valid currencies (expressed using ISO 4217 alpha code) for this order based on the values supplied in the request parameters.
For example, AUD stands for Australian Dollar.
Data must consist of the characters A-Z
Information on the supported sources through which the order can be received.
Enumeration
ALWAYS PROVIDED
Indicates the channel through which you received authorization for the payment for this order from the payer.
For example, set this value to INTERNET if the payer initiated the payment online.
If you have an existing agreement with the payer that authorizes you to process this payment (for example, a recurring payment) then set this value to MERCHANT. You only need to provide transaction.source if you want to override the default value configured for your acquirer link.
Note:
- You can only override the default value if you have the requisite permission.
- The value you provide must match one of those configured by ANZ Worldline Payment Solutions.
- You can only set the transaction source on the initial transaction on an order. It cannot be changed on subsequent transactions.
Value must be a member of the following list. The values are case sensitive.
CALL_CENTRE
Transaction conducted via a call centre.
CARD_PRESENT
Transaction where the card is presented to the merchant.
INTERNET
Transaction conducted over the Internet.
MAIL_ORDER
Transaction received by mail.
MERCHANT
Transaction initiated by you based on an agreement with the payer. For example, a recurring payment, installment payment, or account top-up.
MOTO
Transaction received by mail or telephone.
PAYER_PRESENT
Transaction where a non-card payment method is presented to the Merchant.
SERVICE_PROVIDER
Transaction reported by the acquirer.
TELEPHONE_ORDER
Transaction received by telephone.
VOICE_RESPONSE
Transaction conducted by a voice/DTMF recognition system.
Details about supported credit and debit card payment options.
Information on whether you are set up to use one or more 3DSecure schemes.
The 3DSecure scheme applicable for an order depends on the card type used to pay for the order.
Enumeration
ALWAYS PROVIDED
The list of valid 3D-Secure schemes supported for this order based on the values supplied in the request parameters.
For example, MasterCard SecureCode, Verified by Visa, JSecure, Diners Club ProtectBuy.
Value must be a member of the following list. The values are case sensitive.
AMEX_SAFE_KEY
J_SECURE
OTHER
PROTECT_BUY
SECURE_CODE
VERIFIED_BY_VISA
Enumeration
The brand name used to describe the card that is recognized and accepted globally.
For many major card types this will match the scheme name. In some markets, a card may also be co-branded with a local brand that is recognized and accepted within its country/region of origin (see card.localBrand).
You may use this information to support surcharging decisions. This information is gathered from 3rd party sources and may not be accurate in all circumstances.
Value must be a member of the following list. The values are case sensitive.
AMEX
American Express
CHINA_UNIONPAY
China UnionPay
DINERS_CLUB
Diners Club
DISCOVER
Discover
JCB
JCB (Japan Credit Bureau)
LOCAL_BRAND_ONLY
The card does not have a global brand.
MAESTRO
Maestro
MASTERCARD
MasterCard
UATP
UATP (Universal Air Travel Plan)
UNKNOWN
The brand of the card used in the transaction could not be identified
VISA
Visa
Indicates capabilities available to you for card payments.
Enumeration
ALWAYS PROVIDED
Indicates capabilities available to you for card payments.
Value must be a member of the following list. The values are case sensitive.
CARD_SECURITY_CODE
Indicates if you are allowed to use the Card Security Check to verify the Card Security Code (CSC) supplied by the cardholder
NO_CARD_SECURITY_CODE_PRINTED_ON_CARD
Indicates if you are allowed to accept payments from credit cards without a Card Security Code (CSC) printed on the card.
Information on the card types supported for this order.
String
ALWAYS PROVIDED
The list of valid card types for this order based on the values supplied in the request parameters.
For example, MasterCard, Visa, American Express.
Data can consist of any characters
Comma separated enumeration
Payments processed using a token generated by a card scheme tokenization service such as Mastercard Digital Enablement Service (MDES) can use two different methods to verify the payment details:
- A cryptogram dynamically generated by the payer's device or the scheme tokenization service, or
- An expiry date and card security code (also known as Dynamic Token Value, DTV) dynamically generated by the scheme tokenization service.
Value must be one or more comma separated members of the following list. The values are case sensitive.
CRYPTOGRAM_3DSECURE
Payments using a scheme token can be processed using the token expiry date and a cryptogram that uses the 3-D Secure format.
DYNAMIC_CSC_AND_EXPIRY
Payments using a scheme token can be processed using a dynamically generated expiry date and card security code (also known as Dynamic Token Value, DTV) provided by the card scheme tokenization service.
Information on the currencies supported for this order.
Upper case alphabetic text
The list of valid currencies (expressed using ISO 4217 alpha code) for this order based on the values supplied in the request parameters.
For example, AUD stands for Australian Dollar.
Data must consist of the characters A-Z
Enumeration
The method used by the payer to provide the funds for the payment.
You may use this information to support surcharging decisions. This information is gathered from 3rd party sources and may not be accurate in all circumstances.
Value must be a member of the following list. The values are case sensitive.
CHARGE
The payer has a line of credit with the issuer which must be paid off monthly.
CREDIT
The payer has a revolving line of credit with the issuer.
DEBIT
Funds are immediately debited from the payer's account with the issuer.
UNKNOWN
The account funding method could not be determined.
Comma separated enumeration
Indicates if the cardholder is required to provide additional information when using a card to pay for the order.
Value must be one or more comma separated members of the following list. The values are case sensitive.
CREDIT_DEBIT_SELECTION
Indicates if the cardholder must be forced to select between using a credit card or a debit card, before entering their card details.
CARD_TYPE_SELECTION
Indicates if the cardholder must be forced to select the card type.This is required when the card is identified as a co-branded card and regulation stipulates that the payer must select the card type.The card type selected by the payer must subsequently be provided in field sourceOfFunds.provided.card.cardType on financial transaction requests.
CARD_SECURITY_CODE_ENTRY
Indicates if the cardholder must be forced to enter the Card Security Code (CSC) when using a credit card to pay for the order.
String
The issuer of the card, if known.
WARNING: This information may be incorrect or incomplete – use at your own risk.
Data can consist of any characters
String
The brand name used to describe a card that is recognized and accepted within its country/region of origin.
The card may also be co-branded with a brand name that is recognized and accepted globally (see card.brand).
You may use this information to support surcharging decisions. This information is gathered from 3rd party sources and may not be accurate in all circumstances.
Data can consist of any characters
Information on valid payment plans for this order based on the values supplied in the request parameters.
String
The end date for the payment plan.
This field is only returned if the plan has a known end date.
Data can consist of any characters
Information on the minimum order amount for the payment plan.
This field is only returned if the plan has a minimum order amount.
Decimal
The minimum order amount for the payment plan.
The configured payment plans will be offered only if the total order amount is greater than or equal to this minimum order amount.
Data is a decimal number.
String
The currency (expressed as an ISO 4217 alpha code) for the minimum order amount.
Data can consist of any characters
Integer
The list of valid values specifying the number of months for which the payment can be deferred.
JSON number data type, restricted to being positive or zero. In addition, the represented number may have no fractional part.
Integer
The list of valid values specifying the number of monthly installments payable by the cardholder.
JSON number data type, restricted to being positive or zero. In addition, the represented number may have no fractional part.
Boolean
Indicates if the payer is charged interest on the payment plan.
JSON boolean values 'true' or 'false'.
String
The identifier for the payment plan.
See Payment Plans for the supported payment plans and their identifiers.
Data can consist of any characters
String
The plan name as specified by you when you defined the parameters for this payment plan.
This field is only returned if applicable for this payment plan
Data can consist of any characters
Enumeration
The payment plan template used to generate this payment plan instance.
This field is only returned if applicable for this payment plan.
Value must be a member of the following list. The values are case sensitive.
PAY_IN_FULL_AFTER_DEFERRAL
PAY_IN_INSTALLMENTS_INTEREST_FREE
PAY_IN_INSTALLMENTS_INTEREST_FREE_AFTER_DEFERRAL
PAY_IN_INSTALLMENTS_WITH_INTEREST
PAY_IN_INSTALLMENTS_WITH_INTEREST_AFTER_DEFERRAL
String
The start date for the payment plan.
This field is only returned if the plan has a known start date.
Data can consist of any characters
Enumeration
The organization that owns a card brand and defines operating regulations for its use.
The card scheme also controls authorization and settlement of card transactions among issuers and acquirers.
Value must be a member of the following list. The values are case sensitive.
AMEX
American Express
CHINA_UNIONPAY
China UnionPay
DINERS_CLUB
Diners Club
DISCOVER
Discover
JCB
JCB (Japan Credit Bureau)
MASTERCARD
MasterCard
OTHER
The scheme of the card used in the transaction could not be identified.
UATP
UATP (Universal Air Travel Plan)
VISA
Visa
String
Tags provide you with additional information about the card.
For example, identifying if it is an EBT (Electronic Benefits Transfer) or Health Benefit Card. You can use this information to support your decisions about accepting payments with this card. The data is encoded in JSON as an object map indexed on the tag name. Some standard tag names are EBT and HEALTH_BENEFIT_CARD_IIAS. If these tags apply to the card, the tag will have value true, otherwise it will be absent. Other tag names with other values might also exist, depending on which acquirer processed the transaction. For example, an EBT card might return value: {"ACME_CARD_IDENTIFIER":"23", "EBT":true} Contact your payment provider if you wish to understand all tags available for your acquirers.
Data can consist of any characters
Information on the supported sources through which the order can be received.
Enumeration
ALWAYS PROVIDED
Indicates the channel through which you received authorization for the payment for this order from the payer.
For example, set this value to INTERNET if the payer initiated the payment online.
If you have an existing agreement with the payer that authorizes you to process this payment (for example, a recurring payment) then set this value to MERCHANT. You only need to provide transaction.source if you want to override the default value configured for your acquirer link.
Note:
- You can only override the default value if you have the requisite permission.
- The value you provide must match one of those configured by ANZ Worldline Payment Solutions.
- You can only set the transaction source on the initial transaction on an order. It cannot be changed on subsequent transactions.
Value must be a member of the following list. The values are case sensitive.
CALL_CENTRE
Transaction conducted via a call centre.
CARD_PRESENT
Transaction where the card is presented to the merchant.
INTERNET
Transaction conducted over the Internet.
MAIL_ORDER
Transaction received by mail.
MERCHANT
Transaction initiated by you based on an agreement with the payer. For example, a recurring payment, installment payment, or account top-up.
MOTO
Transaction received by mail or telephone.
PAYER_PRESENT
Transaction where a non-card payment method is presented to the Merchant.
SERVICE_PROVIDER
Transaction reported by the acquirer.
TELEPHONE_ORDER
Transaction received by telephone.
VOICE_RESPONSE
Transaction conducted by a voice/DTMF recognition system.
Indicates the wallet providers you are enabled and configured for, and that are supported for this order.
Provide details about the Secure Remote Commerce (SRC) wallet interaction.
Upper case alphabetic text
The ISO 3166 alpha-3 country code of the payer's country to be used to present country-specific content to the payer during the Secure Remote Commerce interaction.
This is the default country to be used, unless it is overwritten for this transaction in the interaction.country field.
Data must consist of the characters A-Z
Details regarding the merchant's Secure Remote Commerce (SRC) configuration specific to the scheme
String
ALWAYS PROVIDED
Unique identifier assigned to the merchant (called Digital Payment Application) by the Secure Remote Commerce (SRC) System for this scheme.
Data can consist of any characters
Enumeration
ALWAYS PROVIDED
Scheme for which Secure Remote Commerce (SRC) configuration for the merchant is provided.
Value must be a member of the following list. The values are case sensitive.
AMERICAN_EXPRESS
American Express
MASTERCARD
Mastercard
VISA
Visa
Comma separated strings
A comma separated list of ISO 3166-1 alpha-3 country codes.
The merchant only ships to countries included in this list. For a Secure Remote Commerce (SRC) interaction only shipping addresses with a country contained in the list must be accepted.
Each String represents an ISO 3166-1 alpha-3 code for the country.
Enumeration
ALWAYS PROVIDED
Details about the source of the payment details used for digital payment methods.
Provide this value when you process payments for:
- Device payment methods such as Apple Pay, Android Pay, Samsung Pay, or Google Pay.
- Digital wallets such as Masterpass, Visa Checkout or Amex Express Checkout.
Value must be a member of the following list. The values are case sensitive.
AMEX_EXPRESS_CHECKOUT
Amex Express Checkout wallet provider.
APPLE_PAY
Apple Pay mobile wallet provider.
GOOGLE_PAY
Google Pay mobile wallet provider.
MASTERPASS_ONLINE
MasterPass Online wallet provider.
SECURE_REMOTE_COMMERCE
Secure Remote Commerce (SRC) wallet provider.
VISA_CHECKOUT
Visa Checkout wallet provider.
Details about supported UnionPay SecurePay payment options.
Information on the currencies supported for this order.
Upper case alphabetic text
The list of valid currencies (expressed using ISO 4217 alpha code) for this order based on the values supplied in the request parameters.
For example, AUD stands for Australian Dollar.
Data must consist of the characters A-Z
Information on the supported sources through which the order can be received.
Enumeration
ALWAYS PROVIDED
Indicates the channel through which you received authorization for the payment for this order from the payer.
For example, set this value to INTERNET if the payer initiated the payment online.
If you have an existing agreement with the payer that authorizes you to process this payment (for example, a recurring payment) then set this value to MERCHANT. You only need to provide transaction.source if you want to override the default value configured for your acquirer link.
Note:
- You can only override the default value if you have the requisite permission.
- The value you provide must match one of those configured by ANZ Worldline Payment Solutions.
- You can only set the transaction source on the initial transaction on an order. It cannot be changed on subsequent transactions.
Value must be a member of the following list. The values are case sensitive.
CALL_CENTRE
Transaction conducted via a call centre.
CARD_PRESENT
Transaction where the card is presented to the merchant.
INTERNET
Transaction conducted over the Internet.
MAIL_ORDER
Transaction received by mail.
MERCHANT
Transaction initiated by you based on an agreement with the payer. For example, a recurring payment, installment payment, or account top-up.
MOTO
Transaction received by mail or telephone.
PAYER_PRESENT
Transaction where a non-card payment method is presented to the Merchant.
SERVICE_PROVIDER
Transaction reported by the acquirer.
TELEPHONE_ORDER
Transaction received by telephone.
VOICE_RESPONSE
Transaction conducted by a voice/DTMF recognition system.
Enumeration
ALWAYS PROVIDED
A system-generated high level overall result of the transaction/operation.
Value must be a member of the following list. The values are case sensitive.
FAILURE
The operation was declined or rejected by the gateway, acquirer or issuer
PENDING
The operation is currently in progress or pending processing
SUCCESS
The operation was successfully processed
UNKNOWN
The result of the operation is unknown
Information on the supported payment operations available to the merchant.
Enumeration
ALWAYS PROVIDED
The list of supported payment operations available to the merchant.
For example, AUTHORIZE, PURCHASE.
Value must be a member of the following list. The values are case sensitive.
AUTHORIZE
Merchant has privilege to perform Authorizations.
PURCHASE
Merchant has privilege to perform Purchases
Errors Copied to clipboard
Information on possible error conditions that may occur while processing an operation using the API.
Enumeration
Broadly categorizes the cause of the error.
For example, errors may occur due to invalid requests or internal system failures.
Value must be a member of the following list. The values are case sensitive.
INVALID_REQUEST
The request was rejected because it did not conform to the API protocol.
REQUEST_REJECTED
The request was rejected due to security reasons such as firewall rules, expired certificate, etc.
SERVER_BUSY
The server did not have enough resources to process the request at the moment.
SERVER_FAILED
There was an internal system failure.
String
Textual description of the error based on the cause.
This field is returned only if the cause is INVALID_REQUEST or SERVER_BUSY.
Data can consist of any characters
String
Indicates the name of the field that failed validation.
This field is returned only if the cause is INVALID_REQUEST and a field level validation error was encountered.
Data can consist of any characters
String
Indicates the code that helps the support team to quickly identify the exact cause of the error.
This field is returned only if the cause is SERVER_FAILED or REQUEST_REJECTED.
Data can consist of any characters
Enumeration
Indicates the type of field validation error.
This field is returned only if the cause is INVALID_REQUEST and a field level validation error was encountered.
Value must be a member of the following list. The values are case sensitive.
INVALID
The request contained a field with a value that did not pass validation.
MISSING
The request was missing a mandatory field.
UNSUPPORTED
The request contained a field that is unsupported.
Enumeration
A system-generated high level overall result of the operation.
Value must be a member of the following list. The values are case sensitive.
ERROR
The operation resulted in an error and hence cannot be processed.