Specific information about the payment method Diners and Discover.

Originally known as Diners Club International, Discover acquired it along with its worldwide acceptance network in 2008. Diners & Discover is one of the best-known brands in the US, known for becoming the first independent payment card company globally, producing charge cards and credit cards.

The end-customer selects the Diners and Discover button or logo for online payments and enters the card details to complete the purchase. The following card details are required for Diners and Discover:

  • Card number
  • Expiration date
  • CVV2 security code (which is on the back of the card)

Discover offers their 3D Secure solution, Discover ProtectBuy, to prevent fraud and protect Discover sales for all merchants willing to accept online payments using Discover cards.

Discover is expanding its card base through partnerships and collaborations that include BC Card in South Korea, Dinacard in Serbia, and RuPay in India. These cards act as Discover cards when used for cross-border purchases.


If a shopper of your webshop chooses to pay with Diners/Discover, he will initially need to provide his card details. Upon confirming his card details, Accounting as a Service will redirect him to 3DSx for 2 Factor Authentication.

Diners/Discover as well as Accounting as a Service support payments via authorisation/capture as a standard but you may also choose payments via debit/capture depending on your PSP. The related configuration is part of the onboarding procedure and can be found in the technical application. If you have already been onboarded, please contact us or send us your request for configuration change.

In case you need help or advice, please contact us.

Note: If you choose this payment method, your merchant will also need to have a contract with an acquirer where payment guarantees and/or seller protection is defined.


The settlement for Diners/Discover payments follows the standard technical PSP model in Accounting as a Service.


In case of a refund to be handled as part of a return, you should follow our use case Return creation to trigger the refund procedure in Accounting as a Service. Alternatively, if the refund happens in the context of a goodwill procedure, please follow the use case Good will creation for triggering a goodwill credit within Accounting as a Service.

Disputes & Chargeback

Consumers can issue chargebacks. In this case the acquirer will forward a chargeback request to the merchant, who can then try to avoid the chargeback by proving the transaction e.g. by providing an invoice copy and a proof of delivery or proof of usage. Nevertheless some chargebacks can usually not be avoided. In this case the acquirer will debit the chargeback amount in the settlement file, Accounting as a Service will book it on the debtor account and either start the dunning flow (if configured) or write-off the chargeback and correct the VAT for the merchant. There is a notification to inform merchants about chargebacks to enable them to e.g. block services or customer accounts

Please note that managing/defending dispute & chargebacks is part of Accounting as a Service's communication related service and can be enabled and configured during your onboarding as part of the technical application).

See also