Payment methods

An overview of all payment methods currently supported by Accounting as a Service.

There are a number of ways in which a merchant can receive payments from a customer. A payment method represents a specific type of payment, such as payments using a VISA card or payments via PayPal. When working with the payment module of Accounting as a Service, there is a variety of payment methods that is supported.

Type overview

There exist different types of payment methods. Accounting as a Service provides the following method types:

  • Buy now, pay later (BNPL) BNPL related methods allow your customers to purchase your products/services or licences and to pay after delivery.
  • Card payments Card payments refer to the traditional payment system issued by financial institutions, such as a bank. The payment method is based on a physical card. The card enables the owner (i.e. the cardholder) to access the funds in the cardholder's designated (bank) account, to make payments by electronic funds transfer
  • Online payments Online payments (i.e. online bank transfers) are a payment method that enables shoppers to make the payment directly when ordering the product. The Payment Gateway sends the payment confirmation for this payment mode in real-time. After a successful payment, the shopper may no longer revoke the transaction, and the merchant can ship the ordered product or service immediately.
  • Wallet payments (Digital) wallets can be used for online payments with a saved card or a digital wallet balance. Wallet payments allow shoppers to pay merchants they want to do business with directly from their wallets. Just like with online payments, shoppers are enabled to directly handle the payment when ordering the product. Also, payment confirmation for this payment mode is normally sent in real time. In summary, wallet payments are in many cases a payment method with real added value that helps increase conversion rates for merchants and customer satisfaction.
  • Others Beside "buy now, pay later" or any payment method related to card, online or wallet payments, there are some special payment methods such as loyalty cards, prepayment or gift cards that don't fall under any of the specified groups. You will find these methods listed here in the section called "Others".

Payment method overview

Below you will find an overview of all payment methods currently supported by Accounting as a Service. Due to the different nature of each payment method, please note that not every method is working via the pre-built UI solution. Also, when it comes to the 2 different types of payment execution options, some methods are limited to the support of only one out of the 2 options.

In some parts, you might need to refer to a specific payment method (or a list of payment methods) when working with Accounting as a Service and its APIs. For this purpose, each payment method has a unique identifier.

In some cases, the information about the Payment Service Provider (PSP) in charge is relevant for the unique identifier. For this reason, some methods have a list of PSP specific unique identifiers (rather than a single unique identifier). This type of differentiation is needed as the requested payment method related information (such as the cardholder information for credit cards) may depend on the PSP that you work with.

IMPORTANT NOTE: In case of multiple unique identifiers available, the decision about which identifier to choose depends on your configuration. The payment setup is part of the onboarding procedure. Please refer to Step 4: Payment methods of the technical application form for additional information.

Examples where the unique identifier will be needed:

  • Pre-built UI solution: When working with the pre-built UI solution of Accounting as a Service, you may want to refer to specific payment methods. For more information, check out the field paymentMethods of the WidgetAPIOptions on the page explaining the integration with the pre-built UI solution.
  • Create webshop order: The information about the payment method that was used in the scope of a received order need to be provided when creating a webshop order via the API of the accounting module. For this purpose, the unique identifier of the affected payment method needs to be provided as part of the request.

The table below provides an overview of all payment methods supported by Accounting as a Service including the information about related unique identifier(s).

Payment method Supports
& capture
in 2 steps
& capture
in 1 step
by pre-built
UI solution
Unique identifier
Open invoice - - X OpenInvoice
X - X AfterPayOpenInvoice
X - X Klarna (1)
X - X KlarnaOpenInvoice (2)
X - X KlarnaPayLater (3)
SEPA Direct Debit - - X ArvatoDirectDebitSepa (4)
X - X AfterPayDirectDebit
X - X Klarna (1)
X - X KlarnaOpenInvoice (2)
X - X KlarnaPayLater (3)
Instalments X - X AfterPayInstallmentsOpenInvoice
X - X AfterPayInstallmentsDirectDebit
X - X Klarna (1)
X - X KlarnaInstallments (2)
X - X KlarnaPayOverTime (3)
Visa X X X Visa
MasterCard X X X MasterCard
Amex X X X AmericanExpress
Diners X X X DinersClub
Discover X X X Discover
Bancontact - X X Bancontact
Blik - X X Blik
- X X BlikCodeOnly
EPS - X X Eps
Giropay - X X Giropay
iDEAL - X X Ideal
Multibanco - X X Multibanco
P24 - X X Przelewy24
PayU - X X PayU
Sofort - X X Sofort
Trustly - X X Trustly
PayPal X X X PayPal
X X X PayPalExpressCheckout
Amazon Pay X X - AmazonPay
Apple Pay X X - ApplePayExpressCheckout
Google Pay X X - GooglePay
Cash on Delivery - - - CashOnDelivery
Giftcard - - - Giftcard
In-App Purchases - - - InAppAmazon
- - - InAppGoogle
- - - InAppApple
Loyalty Card - - - LoyaltyCard
Omnichannel Payment - - - InStorePrepayment
- - - InStoreOpenInvoice
- - - InStorePickup
Prepayment - - - PrePayment

Additional hints

  • (1) In case the collection is done by Riverty; Redirect
  • (2) In case you have your own contract with Klarna
  • (3) In case the collection is done by Adyen
  • (4) White Label Solution (with collection is done by Riverty or via your own bank account)