Skip to main content
Aria Knowledge Central


Note: This payment gateway has been deprecated.

Supported Payment Methods and Credit/Debit Cards


  • Credit/Debit Card
  • Tokenized Card


  • Visa
  • MasterCard
  • American Express
  • Discover
  • Diners Club/Carte Blanche
  • Maestro
  • JCB (Japan Credit Bureau)
  • Dankort

Supported Features

  • Card Verification Value (CVV)
  • Soft Descriptors
  • $1 Auth and Auth Reversal ($0 Auth is NOT supported)
  • 3D Secure 1.0 (3D Secure 2.0 is not available at this time)

Aria Configuration Fields

Aria Configuration Fields can be overridden if the values are populated in API calls.

  • end_user_ip_address: IP Address that was used to place online order.
  • end_user_browser_accept_header: HTTP Accept Header from the customer's browser. Here is an example: "text/html, application/xhtml+xml, application/xml;q=0.9*/*;q=0.8."
  • end_user_browser_agent: HTTP Agent Header from the customer's browser. Here is an example: "Mozilla /5.0 (Compatible MSIE 9.0;Windows NT 6.1;WOW64; Trident/5.0)."
  • soft_descriptor: Transaction description that may display on the buyer's credit card statement using a more descriptive Merchant Name or Item Description. This field can be used to send extra information from the merchant to the acquiring bank. However, it does not affect what shows up on the bank statement without an explicit agreement from the acquirer to process the data.

    Aria's clients should determine whether the acquiring bank can process the data in the "P-60 field" and add that to the statement. Aria has chosen to support this via the "misc info" part of the field, and its max length is 15 (including the prefix, delimiter and value). Aria will hardcode the prefix and delimiter as "A:".

    Please note: DIBS does not support this field for refunds.

Backend Processors

  • American Express
  • Babs
  • Barclays
  • Cekab
  • Deutsche Card Services
  • Dibs
  • DibsEuroline
  • DibsNordealNorway
  • DibsPBS
  • Elavon
  • Evry PF
  • FirstCard
  • Invik
  • Luottokunta
  • Masterpass Production
  • Masterpass Sandbox (test)
  • NatWestDirect
  • Netpay SHB
  • Pbs
  • TestAcquirer
  • Valitor
  • Wirecard

Specifying a Backend Processor

Within the Aria UI under Configuration > Payment > Collection Groups, you can specify a backend processor when creating a Collection Group.

For the DIBS DT payment processor, you can also specify a backend processor by selecting a value for the Payment Acquirer (DIBS Method) field on the Gateway Options tab in the Aria UI under Configuration > Payments > Payment Gateways > DIBS DT.

Configuration Notes

  • DIBS does not perform AVS validations.
  • DIBS does not return any separate response fields for CVV validations (the "CVC wrong" comes as the main response when they decline the transaction itself).
  • DIBS is not ready with CIT/MIT support (recurring transaction indicator).
  • DIBS does not support querying for the token details; retrieve card details (e.g. expiry month/year, card type) from customers themselves, if required.
  • China UnionPay is not supported.


Regarding Processor/Gateway Integration Certifications

If you previously implemented a custom payment processor/gateway integration, you likely completed a certification process with that processor/gateway. Aria maintains certifications with each of the processors with which it integrates. Though you may wish to certify your Aria-related processor/gateway integration before going live on Aria, this is not necessary and could add significant time and Services costs to your Aria implementation process. Please consult your Aria Implementation representative for more detailed information.

Regarding Processor- and Gateway-specific Information

All Processor- and Gateway-specific information provided on Knowledge Central exists as publicly accessible information from the respective companies, and is presented here for your convenience. We update this information from time to time as necessary.

  • Was this article helpful?