Transaction Options
This class can be used to specify miscellaneous options related to the transaction.
Properties
Your unique callback scheme to be used by the external web process (for example PayPal) to return to the merchant app.
Specify the BoncardConfig object here. This can be used to configure how the ch.datatrans.payment.paymentmethods.PaymentMethodType.BONCARD payment method type should be displayed in the SDK. If not specified, a default value will be used.
Use this setting to choose which label to display for the card option in the payment method selection: "Credit card", "Debit card", or "Credit or debit card". The latter is used by default.
Sometimes, apps display a loading animation before starting the SDK. You can set the customInitialLoader option if you want to keep showing this animation instead of the SDK’s loader during initial SDK network requests. IMPORTANT: Your loader must be visible before starting the SDK. Be aware that the SDK blocks user input. Your loading screen can not have a cancel button or give the impression that users can still interact with the UI.
Specify the GooglePayConfig object here. This is mandatory for Google Pay transactions.
Specify the KlarnaConfig object here for customizing the Klarna payment option. If not specified, default values will be used.
Specify the SamsungPayConfig object here. This is mandatory for Samsung Pay transactions.
Specify this option to control when the DCC (Dynamic Currency Conversion) screen is presented for payments with saved cards (alias/tokenized payments). The default is DCCShowMode.ALWAYS, meaning DCC is always shown when available. See DCCShowMode for additional information.
Use this setting to display or hide critical errors.
Whether secure connections to Datatrans servers require a certificate chain signed with a specific CA private key. The device's trust settings are explicitly ignored, i.e. custom installed/white-listed certificates and/or CAs will not work.