Skip to main content
Aria Knowledge Central



Supported Payment Methods and Credit/Debit Cards


  • Credit Card
  • Tokenized Credit Card
  • Direct Debit (SEPA)
  • ApplePay—Indirect
  • PayPal Express Checkout—Indirect
  • Giropay
  • Klarna
  • Qiwi
  • WebMoney
  • Yandex


  • Visa
  • MasterCard
  • American Express
  • Discover
  • JCB
  • Elo
  • Hipercard
  • Maestro

Note: Recurring payments are currently not supported for SOFORT, Giropay, Klarna, Qiwi, WebMoney and Yandex APMs (Alternate Payment Methods) and refund transactions are supported for all APMs except Giropay.

Note: The Qiwi and Yandex payment methods are unavailable until further notice.

Supported Features

Aria Configuration Fields

Getting Here: Add or edit a payment gateway and/or collection group.

  • Web Services Username: Unique user identifier configured in Worldpay's Merchant Administration Interface
  • Web Services Password: Unique user password configured in Worldpay's Merchant Administration Interface
  • Web Services URL: Worldpay Server API endpoint for Worldpay sandbox, pre-production, or production environments. You must include "https://" in this string.
  • Merchant Number: Unique value provided by WorldPay used as part of a "mandateId" required for SEPA Direct Debit transactions.
  • Payer Authentication Settings: If you want to use 3D Secure (3DS) authentication 2.0, complete all fields under Payer Authentication Settings. If you leave these fields blank, Aria will use 3DS 1.0.

    Please contact Worldpay to get these URLs: DDC Posting URL and Challenge Posting URL.

    Please contact your payment gateway representative for more information.

Configuration Notes

Please contact your payment gateway representative for more information.

  • To accept payments from customers using SEPA Direct Debit, you must first specify your merchant number, which you can obtain from your WorldPay representative. You can specify only one merchant number at the payment gateway level and create multiple collection groups with different merchant numbers based on your requirements.
  • Because of a limitation associated with SEPA Direct Debit, Aria does not recommend using authorize and capture in the same API call for payments made using that payment method. Instead, you should first make an authorize API call (example: authorize_electronic_payment), confirm that the order has been moved into the authorized status, then attempt to make a capture API call (example: collect_from_account). This will ensure that a payment is authorized before the payment is captured and the account balance is reduced.


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?