Payment Methods

Cards

Description

Virtual Terminal allows you to accept debit and credit card payments on your PC, smartphone or tablet, as long as you have internet access. A virtual payment terminal is an ID assigned to the merchant (MID) which allows you to accept VISA and MASTERCARD cards in your e-commerce store or application.

Integration Options

Payment Scenarios

Additional Capabilities

Markets

Currencies

Transaction Limits

How to Enable Card Payments


Apple Pay

Description

We support Host2Host integration, thus you as a merchant are responsible for the interactions with the Apple Pay API. Once you have completed those interactions, we will consume the payment data. With Host2Host integration, you are in complete charge of how to integrate Apple Pay into your website or app; therefore, we do not control, nor provide assistance for it. You can find the design guidelines and the information about Apple Pay button usage in the Apple Pay Human Interface Guidelines The information about server requirements for Apple Pay on the web can be found in the Apple Developer Portal.

Please note that your customers will be able to choose Apple Pay as a payment method option only when they:

  • Are located in a region where Apple Pay is supported (see the full list here);
  • Have an existing card added to their Apple Pay wallet;
  • Use Safari browser when paying on the website;
  • Use an Apple Pay compatible device.

Before you start enabling this payment method, make sure that your DECTA account manager has given you Apple Pay permission.

Integration Options

Payment Scenarios

Additional Capabilities

Markets

Currencies

Transaction Limits

How to Enable Apple Pay

Payment Flow


Google Pay™

Description

For Google Pay™ we support Host2Host integration, thus you as a merchant are responsible for the interactions with the Google Pay API. Once you have completed those interactions, we will consume the payment data. Follow the Google Pay guidelines to integrate your web or Android application:

Google Pay offers and we support two authentication modes:

  • PAN_ONLY - the card is stored on file within your customer's Google account and not bound to an Android device. 3DS/Authentication is handled automatically by the DECTA Gate;
  • CRYPTOGRAM_3DS - cards stored in the Google Pay Wallet on the Android device. This method is considered fully authenticated, thus 3DSecure is not needed here.

Supported networks:

  • Visa - supported globally;
  • Mastercard - supported globally.

Before you start enabling this payment method, make sure that your DECTA account manager has given you Google Pay permission.

Integration Options

Payment Scenarios

Markets

Currencies

Transaction Limits

How to Enable Google Pay

Payment Flow


PayPal

Description

We offer PayPal payments via Host2Host integration and Full Page and Embedded Iframe integrations. For a Host2Host integration with PayPal, you as a merchant are responsible for redirecting your customers to the PayPal environment. You are in complete charge of how to integrate PayPal into your website or app. To create an optimal payment experience, make sure your integration meets the PayPal design guidelines. The information about server requirements for PayPal can be found in the PayPal developer section.

For Full Page and Embedded Iframe integrations, we generate a hosted payment page (also in the form of an embeddable iframe) that handles the redirections of your customers to PayPal directly for their credential and payment data collection.

Please note that your customers will be able to choose PayPal as the payment method if they are located in a region where PayPal is supported.

Before you start enabling this payment method, make sure that your DECTA account manager has given you PayPal permission.

Integration Options

Payment Scenarios

Markets

Currencies

Transaction Limits

How to Enable PayPal

Payment Flow


Volt

Description

We currently offer Volt payments via Host2Host and Full Page integrations. For a Host2Host integration with Volt, you as a merchant are responsible for displaying the payment method option on your checkout page and redirecting your customers to the Volt environment. Volt brand logos for your checkout page can be found here.

For Full Page integration, DECTA generates a hosted payment page that directly handles the redirections of your customers to Volt for the credential and payment data collection. Please see our API documentation for more information.

Note that your customers will be able to choose Volt as the payment method only if the currency they are using is EUR.

Before you start enabling this payment method, make sure that your DECTA account manager has given you the Volt permission.

Integration Options

Payment Scenarios

Markets

Currencies

Transaction Limits

How to Enable Volt

Payment Flow


Zimpler

Description

We currently offer Zimpler payments via Host2Host. For a Host2Host integration with Zimpler, you as a merchant are responsible for displaying the payment method option on your checkout page and redirecting your customers to the Zimpler environment.

Before you start enabling this payment method, make sure that your DECTA account manager has given you the Zimpler permission. Zimpler logo files are available upon request from our support team.

Please note that DECTA will delete all KYC data from the payment objects, except zimpler_user_id and country, after 30 days.

Integration Options

Payment Scenarious

Markets

Currencies

Transaction Limits

How to Enable Zimpler

Payment Flow

Payout Flow


Open Banking

Description

We currently offer DECTA Open Banking payments with Host2Host, Full Page, and Payform WEB SDK integration options. For the Host2Host integration with DECTA, you as a merchant are responsible for displaying the payment method option on your checkout page and redirecting your customers to the DECTA Open Banking environment.

Before you start enabling this payment method, make sure that your DECTA account manager has given you Open Banking permission. DECTA Open Banking logo files are available upon request from our support team.

Open Banking method is one of those methods which may have a delayed confirmation from the payment provider. Depending on the provider, the payment confirmation in some cases can be delayed from a couple of minutes to multiple days. For such cases we advise sending us the in_progress_redirect parameter in the order request, which will be used to redirect your customer back to you in case a confirmation is not received within 3 minutes after returning to the Gateway. Once the Gateway will receive a confirmation from the payment provider, you will receive an appropriate webhook with a new status of the payment. Make sure that the URL you use for such redirects clearly explains to your customers that the payment has been successfully processed but requires additional time for the final confirmation. You should also state that, after receiving the final confirmation, you will notify your customers about its result via different means.

Integration Options

Payment Scenarious

Markets

Currencies

Transaction Limits

How to Enable Open Banking

Payment Flow


Jump to
  • Cards
  • Apple Pay
  • Google Pay™
  • PayPal
  • Volt
  • Zimpler
  • Open Banking