• Host2Host

• One-Step Payment
• Two-Step Payment
• Full Refund
• Partial Refund
• Reversal
• Recurring

• Payment Method Saving
• Use of Travel Data
• Use of Account Funding details
• Automatic Billing Updater

South Africa, Australia, China (mainland), Hong Kong, Japan, Macao, New Zealand, Singapore, Taiwan, Armenia, Austria, Azerbaijan, Belarus, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Faroe Islands, Finland, France, Georgia, Germany, Greece, Greenland, Guernsey, Hungary, Iceland, Ireland, Isle of Man, Italy, Kazakhstan, Jersey, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Monaco, Montenegro, Netherlands, Norway, Poland, Portugal, Romania, Russian Federation, San Marino, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Ukraine, United Kingdom, Vatican, Argentina, Colombia, Costa Rica, Brazil, Mexico, Peru, Bahrain, Israel, Palestine, Qatar, Saudi Arabia, United Arab Emirates, Canada, United States.

USD, GBP, EUR, RUB, AUD, SEK, CAD, CHF, DKK, JPY, PLN, CZK, NOK, AED, BYN, CNY, KZT, NZD, UAH, AZN, GEL, KGS, UZS, ZAR, AMD, ARS, BGN, BRL, CLP, EGP, HKD, HRK, HUF, IDR, ILS, INR, ISK, KES, KRW, LKR, MAD, MDL, MKD, MOP, MUR, MXN, MYR, NGN, PEN, PHP, QAR, RON, RSD, SAR, SGD, THB, TJS, TMT, TRY, TWD, UYU, VND, ZWL.

Transaction limits differ for each currency and market. If you want to find out more about a particular market or currency, contact your DECTA account manager.

1. Log in to your Apple Developer account and follow the instructions to create a merchant identifier and merchant identity certificate (assigned to the identifier);
2. Go to your DECTA Gate account, select Settings, then the Payment Methods section and click on the "Configure" button for Apple Pay;
3. Click on the “Add new certificate", select the appropriate website, enter the domain name, and then click "Add";
4. After adding a new certificate, it will appear in the Apple Pay Certificates section with status pending. In order to activate it, click on the Actions menu and choose to upload a certificate. A new view will be presented where you download the CSR file. Then, go to your Apple Developer account and follow these instructions to create a payment processing certificate.
   NB: Make sure you use the same merchant identifier as in the previous steps. When you are asked to upload a Certificate Signing Request, select the CSR you just downloaded from the Merchant Portal. Then, download and save the generated payment processing certificate as a .cer file. Now you can upload the certificate you received from Apple in the Merchant Portal. Once that is done, click “Add”;
5. You will now see the certificate attached to your application. The status - pending or active - indicates whether the certificate is active. If it is, you are now able to perform Apple Pay transactions with DECTA;

6. This step is required only if you are integrating Apple Pay with your app. Ignore this step, if you intend to integrate Apple Pay with your website only.
   In order to enable Apple Pay for an app, log in to your Apple Developer account and follow these instructions.

• Host2Host

• One-Step Payment
• Two-Step Payment
• Full Refund
• Partial Refund
• Reversal
• Recurring

• Payment Method Saving
• Use of Travel Data
• Use of Account Funding details
• Automatic Billing Updater

Afghanistan, Albania, Algeria, Andorra, Angola, Antigua and Barbuda, Argentina, Armenia, Australia, Austria, Azerbaijan, Bahamas, Bahrain, Bangladesh, Barbados, Belarus, Belgium, Belize, Benin, Bhutan, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, Brunei, Bulgaria, Burkina Faso, Burundi, Cambodia, Cameroon, Canada, Cape Verde, Central African Republic, Chad, Chile, Colombia, Comoros, Costa Rica, Côte d'Ivoire, Croatia, Cyprus, Czech Republic, Democratic Republic of the Congo, Denmark, Djibouti, Dominica, Dominican Republic, Ecuador, Egypt, El Salvador, Equatorial Guinea, Eritrea, Estonia, Eswatini, Ethiopia, Fiji, Finland, France, Gabon, Gambia, Georgia, Germany, Ghana, Greece, Grenada, Guatemala, Guinea, Guinea-Bissau, Guyana, Haiti, Holy See, Honduras, Hong Kong, Hungary, Iceland, India, Iraq, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kazakhstan, Kenya, Kiribati, Kuwait, Kyrgyzstan, Laos, Latvia, Lebanon, Lesotho, Liberia, Libya, Liechtenstein, Lithuania, Luxembourg, Macau, Madagascar, Malawi, Malaysia, Maldives, Mali, Malta, Marshall Islands, Mauritania, Mauritius, Mexico, Micronesia, Moldova, Monaco, Mongolia, Montenegro, Morocco, Mozambique, Myanmar, Namibia, Nauru, Nepal, Netherlands, New Zealand, Nicaragua, Niger, Nigeria, North Macedonia, Norway, Oman, Pakistan, Palau, Palestine, Panama, Papua New Guinea, Paraguay, Peru, Poland, Portugal, Qatar, Republic of the Congo, Romania, Rwanda, Saint Kitts and Nevis, Saint Lucia, Saint Vincent and the Grenadines, Samoa, San Marino, Sao Tome and Principe, Saudi Arabia, Senegal, Sierra Leone, Serbia, Seychelles, Singapore, Slovakia, Slovenia, Solomon Islands, Somalia, South Africa, South Sudan, Spain, Sri Lanka, Sudan, Suriname, Sweden, Switzerland, Taiwan, Tajikistan, Tanzania, Thailand, Timor-Leste, Togo, Tonga, Trinidad and Tobago, Tunisia, Turkey, Turkmenistan, Tuvalu, Uganda, Ukraine, United Arab Emirates, United Kingdom and outlying territories, United States and outlying territories, Uruguay, Uzbekistan, Vanuatu, Venezuela, Vietnam, Yemen, Zambia, Zimbabwe

USD, GBP, EUR, RUB, AUD, SEK, CAD, CHF, DKK, JPY, PLN, CZK, NOK, AED, BYN, CNY, KZT, NZD, UAH, AZN, GEL, KGS, UZS, ZAR, AMD, ARS, BGN, BRL, CLP, EGP, HKD, HRK, HUF, IDR, ILS, INR, ISK, KES, KRW, LKR, MAD, MDL, MKD, MOP, MUR, MXN, MYR, NGN, PEN, PHP, QAR, RON, RSD, SAR, SGD, THB, TJS, TMT, TRY, TWD, UYU, VND, ZWL

Transaction limits differ for each currency and market. If you want to find out more about a particular market or currency, contact your DECTA account manager.

Contact your DECTA account manager to enable this payment method.

• Host2Host
• Full Page
• Payform JS SDK

• One-Step Payment
• Two-Step Payment
• Full Refund
• Partial Refund

Albania, Algeria, Andorra, Angola, Anguilla, Antigua and Barbuda, Argentina, Armenia, Aruba, Australia, Austria, Azerbaijan, Bahamas, Bahrain, Barbados, Belarus, Belgium, Belize, Benin, Bermuda, Bhutan, Bolivia, Bosnia and Herzegovina, Botswana, Brazil, Brunei, Bulgaria, Burkina Faso, Burundi, Cabo Verde, Cambodia, Cameroon, Canada, Cayman Islands, Chad, Chile, China, Colombia, Comoros, Congo, The Democratic Republic of the Congo, Cook Islands, Costa Rica, Croatia, Cyprus, Czech Republic, Côte d'Ivoire, Denmark, Djibouti, Dominica, Dominican Republic, Ecuador, Egypt, El Salvador, Eritrea, Estonia, Ethiopia, Falkland Islands, Faroe Islands, Fiji, Finland, France, French Guiana, French Polynesia, Gabon, Gambia, Georgia, Germany, Gibraltar, Greece, Greenland, Grenada, Guadeloupe, Guatemala, Guinea, Guinea-Bissau, Guyana, Honduras, Hong Kong, Hungary, Iceland, India, Indonesia, Ireland, Israel, Italy, Jamaica, Japan, Jordan, Kazakhstan, Kenya, Kiribati, South Korea, Kuwait, Kyrgyzstan, Laos, Latvia, Lesotho, Liechtenstein, Lithuania, Luxembourg, Macedonia, Madagascar, Malawi, Malaysia, Maldives, Mali, Malta, Marshall Islands, Martinique, Mauritania, Mauritius, Mayotte, Mexico, Micronesia, Moldova, Monaco, Mongolia, Montenegro, Montserrat, Morocco, Mozambique, Namibia, Nauru, Nepal, Netherlands, Netherlands Antilles, New Caledonia, New Zealand, Nicaragua, Niger, Nigeria, Niue, Norfolk Island, Norway, Oman, Palau, Panama, Papua New Guinea, Paraguay, Peru, Philippines, Pitcairn, Poland, Portugal, Qatar, Romania, Russian Federation, Rwanda, Réunion, Saint Helena, Saint Kitts and Nevis, Saint Lucia, Saint Pierre and Miquelon, Saint Vincent and the Grenadines, Samoa, San Marino, Sao Tome and Principe, Saudi Arabia, Senegal, Serbia, Seychelles, Sierra Leone, Singapore, Slovakia, Slovenia, Solomon Islands, Somalia, South Africa, Spain, Sri Lanka, Suriname, Svalbard and Jan Mayen, Swaziland, Sweden, Switzerland, Taiwan, Tajikistan, Tanzania, Thailand, Togo, Tonga, Trinidad and Tobago, Tunisia, Turkmenistan, Turks and Caicos Islands, Tuvalu, Uganda, Ukraine, United Arab Emirates, United Kingdom, United States, Uruguay, Vanuatu, Vatican, Venezuela, Vietnam, British Virgin Islands, Wallis and Futuna, Yemen, Zambia, Zimbabwe.

USD, GBP, EUR, RUB, AUD, SEK, CAD, CHF, DKK, JPY, PLN, CZK, NOK, CNY, NZD, AMD, BRL, HKD, HUF, ILS, MXN, MYR, PHP, SGD, THB, TWD.

Transaction limits differ for each currency and market. If you want to find out more about a particular market or currency, contact your DECTA account manager.

1. Log in to your DECTA Gate account, go to Settings, select the Payment Methods section and click on the “Enable” button for PayPal. You will be automatically redirected to the PayPal environment;
2. Once you are redirected to the PayPal environment, you will be asked either to log in with your existing PayPal account or register a new one. If you have a personal PayPal account, you can use that one as well in this step, just take into account that later on you will be asked to upgrade it to a business account. Fill out all the required fields and accepts terms and conditions, allowing to connect your DECTA account with your PayPal account. In case you used your personal account, you will receive a verification link to your email for upgrading your account;
3. Once the approval from the PayPal side will be received, you will see in your Gate account that PayPal status has been activated. Now you can start accepting PayPal payments.

Common Order Request Example

Once you have successfully enabled PayPal for your account, you can start to accept PayPal payments. You as a merchant create the initial order. Example:

{
  //required
  "client":{
    "email": "jane.doe@company.com"
  },
  "products": [
    {
      "quantity": "1",
      "price": "0.30",
      "title": "My Product"
    }
  ]
}

As a response from DECTA you will receive a parameter called api_init_paypal.

Full Page

If you are using the DECTA hosted payment page, no technical changes are required from your side. Once you redirect your customer to the appropriate URL, they will be able to choose whether to pay by card or by PayPal. All communication with PayPal during the payment process is handled by DECTA.

Payform JS SDK

If you are using the DECTA Payform JS SDK, no technical changes are required from your side. Customer will be able to choose on payform whether to pay by card or by Volt. All communication with Volt during the payment process is handled by DECTA.

Host2Host

1. Create a POST request to PayPal api_init_paypal endpoint and as a response you will receive a parameter approve_url;
2. Redirect your customer to the approve URL received in the previous step;
3. The customer can now either authorise the PayPal payment or cancel it;
4. If the customer authorises the payment, PayPal will redirect the customer to the return URL;
5. DECTA will proceed either to capturing or holding the payment, according to the merchant’s choice;
6. After a successfully proceeded payment, your customer will be redirected to the success page.

Note that the payment amount and currency should match the amount and currency in the order.

• Host2Host
• Full Page
• Payform JS SDK

• One-Step Payment

Andorra, Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Liechtenstein, Lithuania, Luxembourg, Malta, Monaco, Netherlands, Norway, Poland, Portugal, Romania, San Marino, Slovakia, Slovenia, Spain, Sweden, Switzerland, United Kingdom, Vatican.

GBP, EUR, SEK, CHF, DKK, PLN, CZK, NOK, BGN, HRK, HUF, ISK, RON

Transaction limits differ for each currency and market. If you want to find out more about a particular market or currency, contact your DECTA account manager.

1. Log in to your DECTA Gate account, go to Settings, select the Payment Methods section and click on the “Configure” button for Volt;
2. Click on the "Add new brand" and select the brand for which you would like to add Volt payment method;
3. Choose the brand and wait for your DECTA account manager to set up and approve your request. Once it is approved, the status next to the chosen brand will change from Pending to Approved.

Common Order Request Example

Once you have successfully enabled Volt for your account, you can start to accept Volt payments. You as a merchant create the initial order. Example:

{
  //required
  "client":{
    "email": "jane.doe@company.com"
  },
  "products": [
    {
      "quantity": "1",
      "price": "0.30",
      "title": "My Product"
    }
  ],
  //optional
  "success_redirect": "https://example.com/success",
  "failure_redirect": "https://example.com/failure",
  "currency": "EUR"
}

As a response from DECTA you will receive a parameter called api_init_volt. Note that:

• The success_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The failure_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The currency field is optional: if the currency value is not provided in the order body by the merchant, then it will be taken from the terminal settings.

Full Page

If you are using the DECTA hosted payment page, no technical changes are required from your side. After you redirect your customer to the appropriate URL, they will be able to choose whether to pay by card or by Volt. All communication with Volt during the payment process is handled by DECTA.

Payform JS SDK

If you are using the DECTA Payform JS SDK, no technical changes are required from your side. Customer will be able to choose on payform whether to pay by card or by Volt. All communication with Volt during the payment process is handled by DECTA.

Host2Host

Once you have successfully implemented Volt payment buttons on your website or app, you can begin to initiate Volt payments:

1. Create a POST request to Volt api_init_volt endpoint and as a response you will receive a parameter volt_approve_url;
2. Redirect your customer to the approve URL received in the previous step;
3. The customer can now either authorise the Volt payment or cancel it;
4. If the customer authorises the payment, then Volt will redirect the customer to the return URL;
5. DECTA captures the payment;
6. After successfully proceeded payment, the customer is redirected to the success page.

Note that the payment amount and currency should match the amount and currency in the order.

• Host2Host

• One-Step Payment
• Payouts

Estonia, Finland, Netherlands, Sweden

EUR, SEK

1. Log in to your DECTA Gate account, go to Settings, select Payment Methods and click on the "Configure” button for Zimpler;
2. Click on the Add new brand and select the brand for which you would like to add Zimpler payment method;
3. Choose the brand and submit your request. The initial request may take up to one week for your DECTA account manager to approve it with Zimpler;
4. Once it is approved, the status next to the chosen brand will change from Pending to Approved.

Common Order Request Example

Once you have successfully enabled Zimpler for your account, you can begin to initiate Zimpler payments:

You as a merchant create the initial order. Example:

{
  //required
  "client":{
    "email": "jane.doe@company.com",
    "country": "EE"
  },
  "products": [
    {
      "quantity": "1",
      "price": "0.30",
      "title": "My Product"
    }
  ],
  //optional
  "success_redirect": "https://example.com/success",
  "failure_redirect": "https://example.com/failure",
  "currency": "EUR"
}

As a response from DECTA you will receive a parameter called api_init_zimpler. Note that:

• The country field is mandatory: if the value is not provided for this field, the api_init_zimpler link won’t be returned. The country field can be provided in either client or original_client object;
• The success_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The failure_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The currency field is optional: if the currency value is not provided in the order body by the merchant, then it will be taken from the terminal settings;

Host2Host

1. Create a POST request to api_init_zimpler endpoint (see the API documentation here) and as a response you will receive a parameter called zimpler_approve_url;
2. Redirect your customer to the approve URL received in the previous step;
3. The customer can now either authorise the Zimpler payment or cancel it. If the payment gets cancelled, DECTA will send a webhook about a failed Zimpler payment and the payment status will be changed to Failed;
4. If the customer authorises the payment, then Zimpler will redirect the customer to the success URL. As seen above in the order body example, the merchant can provide their own custom success URL to which the customer should be redirected. If it is not provided, then Zimpler will redirect the customer to the DECTA Gate success URL;
5. DECTA captures the payment – this is done automatically in the background. In case something goes wrong, the payment status will be changed to Failed. In that case it is advised for the merchant to wait for a webhook from DECTA Gate side to change the status on their side;
6. After successfully proceeded payment, the payment status is updated for the merchant by DECTA and an appropriate webhook about the status is sent out.

Payouts can be made only to those customers from whom you have previously accepted successful incoming payments to your account.

Once your DECTA account manager has enabled the Zimpler Payouts permission and you have an allocated outgoing Zimpler terminal, you can start initiating the first payout:

1. You as a merchant create the charge (see the API documentation here - section Orders, endpoint: /orders/init_apm_payout). Example:

   {
     "client": {
       "first_name": "Joe",
       "last_name": "Smith",
       "country": "SE",
       "birth_date": "2000-01-01"
     },
     "amount": 100,
     "currency": "EUR"
   }
   

   As a response from DECTA you will receive a parameter called init_zimpler_payout. Note that:

   • The country field is mandatory: if the value is not provided for this field, the api_init_zimpler link won’t be returned;
   • The value of the country field must be the same as the one provided in the charge order;
   • The currency field is optional: if the currency value is not provided in the order body by the merchant, then it will be taken from the terminal settings.

2. Create a POST request to api_zimpler_payout endpoint (see the API documentation here - section Orders, endpoint: api_do_url_init_zimpler_payout). Example:

   {
     "zimpler_user_id": "123ff1c1-1c11-11a1-ab11-f1fae1a11111",
     "ip_address": "string"
   }
   

   Note that zimpler_user_id is a mandatory field and its value can be found in the response of a previously made, successful Zimpler incoming payment from the same customer.

3. As a response you will receive a parameter zimpler_approve_url that includes a link. That link is merely informative and should not be used for redirection purposes;
4. Zimpler payouts do not require approval or any involvement of the end-user. The merchant has to wait for the webhook from the DECTA side about the payout status, and it is then up to the merchant to decide where the end-user should be redirected.

• Host2Host
• Full Page
• Payform JS SDK

• One-Step Payment

Austria, Bulgaria, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Italy, Latvia, Lithuania, The Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Spain, Sweden, United Kingdom

Please refer to you manager about the markets available to you.

EUR, GBP

Transaction limits may differ for each market. If you want to find out more, contact your DECTA account manager.

1. Log in to your DECTA Gate account, go to Settings, select Payment Methods and click on the "Configure” button for Open Banking;
2. Click on the "Add new brand" and select the brand for which you would like to add DECTA Open Banking payment method;
3. Choose the brand and submit your request. The initial request may take up to one week for your DECTA account manager to approve it;
4. Once it is approved, the status next to the chosen brand will change from Pending to Approved.

Common Order Request Example

Once you have successfully enabled Open Banking for your account, you can start to accept Open Banking payments. You as a merchant create the initial order. Example:

{
  "client":{
    "email": "example@mail.com"
  },
  "products": [
    {
      "price": "10",
      "title": "My Product"
    }
  ],
  //optional
  "success_redirect": "https://www.example.com/successful_payment",
  "failure_redirect": "https://www.example.com/failed_payment",
  "in_progress_redirect": "https://www.example.com/in_progress"
}

As a response from DECTA you will receive a parameter called api_init_openbanking. Note that:

• The success_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The failure_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The in_progress_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used.

Full Page

If you are using the DECTA hosted payment page, no technical changes are required from your side. After you redirect your customer to the appropriate URL, they will be able to choose whether to pay by card or via Open Banking. All communication with Open Banking during the payment process is handled by DECTA.

Payform JS SDK

If you are using the DECTA Payform JS SDK, no technical changes are required from your side. Customer will be able to choose on payform whether to pay by card or via Open Banking. All communication with Open Banking during the payment process is handled by DECTA.

Host2Host

1. Create a POST request to api_init_openbanking endpoint (see the API documentation here). Note that this request can be:

   • an empty request

   • containing a common redirect (see step 6 for uses cases):

     {
       "common_redirect": "https://www.example.com/"
     }
     

2. As a response you will receive a parameter called openbanking_approve_url;
3. Redirect your customer to the approve URL received in the previous step;
4. The customer can now either authorise the DECTA Open Banking payment or cancel it;

5. When the customer has approved or declined the payment:

   • The customer will be redirected to the DECTA default success or failure page, if the common redirect is not sent in the step 2;
   • The customer will be redirected straight to your common redirect URL, if it is passed in the step 2 (for a full Host2Host experience);
   • The customer will be redirected to your success, failure, or in progress page, if success, failure, and in progress redirects is sent in step 1 but the common redirect is not sent in the step 2;
6. After successfully proceeded payment, the payment status is updated for the merchant by DECTA and an appropriate webhook about the status is sent out.

• Host2Host
• Full Page
• Payform JS SDK

• Two-Step Payment
• Full Refund
• Partial Refund

Austria, Belgium, Denmark, Finland, Germany, Netherlands, Poland, Sweden, Switzerland, United Kingdom, Australia, Canada, France, Ireland, Italy, Norway, New Zealand, Portugal, Spain, United States of America, Czech Republic, Greece, Romania

CHF, DKK, EUR, GBP, NOK, PLN, SEK, AUD, CAD, USD, CZK, RON, NZD

Transaction limits differ for each currency and market. If you want to find out more about a particular market or currency, contact your DECTA account manager.

1. Log in to your DECTA Gate account, go to Settings, select Payment Methods and click on the "Configure” button for Klarna;
2. Click on the "Add new brand" and select the brand for which you would like to add Klarna payment method;
3. Choose the brand and submit your request. The initial request may take up to one week for your DECTA account manager to approve it;
4. Once it is approved, the status next to the chosen brand will change from Pending to Approved.

Common Order Request Example

Once you have successfully enabled Klarna for your account, you can start to initiate payments. You as a merchant create the initial order. Example:

{
  //required
  "client":{
    "email": "jane.doe@company.com",
    "country": "NL"
  },
  "skip_capture": true,
  "products": [
    {
      "quantity": "1",
      "price": "0.30",
      "title": "My Product"
    }
  ],
  //optional
  "success_redirect": "https://example.com/success",
  "failure_redirect": "https://example.com/failure"
}

As a response from DECTA, you will receive a parameter called api_init_klarna.

Note that:

• The country field is mandatory: if the value is not provided for this field, the api_init_klarna link won’t be returned. The country field can be provided in either client or original_client object;
• The success_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• The failure_redirect field is optional: if the value for it is not provided by the merchant, DECTA Gate default value will be used;
• skip_capture: true is required to make Two-Step Klarna payments.

Full Page

If you are using the DECTA hosted payment page, no technical changes are required from your side. After you redirect your customer to the appropriate URL, they will be able to choose whether to pay by card or via Klarna. All communication with Klarna during the payment process is handled by DECTA.

Payform JS SDK

If you are using the DECTA Payform JS SDK, no technical changes are required from your side. Customer will be able to choose on payform whether to pay by card or via Klarna. All communication with Klarna during the payment process is handled by DECTA.

Host2Host

1. Create a POST request to Klarna api_init_klarna endpoint and as a response you will receive a parameter klarna_approve_url;
2. Redirect your customer to the approve URL received in the previous step;
3. The customer can now either authorise the Klarna payment or cancel it; (will be clarified)
4. When the customer has approved or declined the payment:
   • The customer will be redirected to the DECTA default success or failure page, if the common redirect is not sent in the step 2;
   • The customer will be redirected to your success, failure, or in progress page, if success, failure, and in progress redirects is sent in order request;
5. After a successfully proceeded payment, the payment status is updated for the merchant by DECTA and an appropriate webhook about the status is sent out.

Direct Post

This integration option is not available for Klarna.

• Host2Host
• Full Page
• Payform JS SDK

• One-Step Payment
• Two-Step Payment
• Full Refund
• Partial Refund
• Reversal

• Use of Travel Data
• Use of Dynamic Descriptor
• Use of Service Location details
• Address Verification System

United Kingdom

GBP

Contact your DECTA account manager to enable this payment method.

Common Order Request Example

Once you have successfully enabled Visa Instalments for your account, you can start to accept Visa Instalment payments. You as a merchant create the initial order. Example:

{
  //required
  "client":{
    "email": "adam.smith@company.com"
  },
  "products": [
    {
      "quantity": "1",
      "price": "50",
      "title": "My Product"
    }
  ],
  //optional
  "currency": "GBP"
}

As a response from DECTA you will receive a parameter called instalment_plans.

Full Page

If you are using the DECTA hosted payment page, no technical changes are required from your side. After you redirect your customer to the appropriate URL, they will see if their card is eligable for instalments. If it is, then the customer can select either to pay all amount in full or choose a plan and pay in instalments. Payment processing is the same as for regular orders.

Payform JS SDK

If you are using the DECTA Payform JS SDK, no technical changes are required from your side. Once you customer has submitted their card data, they will see if their card is eligable for instalments. If it is, then the customer can select either to pay all amount in full or choose a plan and pay in instalments. Payment processing is the same as for regular orders.

Host2Host

1. Check if the card is eligible for Visa Instalments and request Instalment plans by sending Visa card number in the request to DECTA Gate instalment_plans endpoint.

Request example:

{
  "card_number": "411111******1111"
}

Response example if the plans are available:

{
  "instalment_request_id": 12,
  "instalment_plans": [
    {
      "id": "string",
      "frequency": "string",
      "number_of_instalments": 3,
      "terms_conditions": [
        {
          "url": "string",
          "version": 4,
          "text": "string",
          "language": "string"
        }
      ],
      "annual_percentage_rate": 3.0,
      "total_amount": 353.5,
      "total_fee": 3.51,
      "amount": 117.83,
      "fee": 1.17
    }
  ]
}

Response example if the plans are not avaible:

{
  "instalment_request_id": "12345",
  "instalment_plans": []
}

2. If the plans are available and the cardholder has selected the desired plan, certain fields from the instalment_plans response should be sent in api_do_url request.

Request example:

{
  "cardholder_name": "GATETEST123",
  "card_number": "411111******1111",
  "exp_month": "05",
  "exp_year": "24",
  "csc": "***",
  "instalment_plan":{
    "instalment_request_id": 123, //taken from /instalment_plans response - mandatory for Instalment plans
    "id": "...", //taken from /instalment_plans response - mandatory for Instalment plans
    "version": 4, //taken from /instalment_plans response - mandatory for Instalment plans
    "language": "eng" //taken from /instalment_plans response - mandatory for Instalment plans
  }
}

3. As a response you will receive either a payment status or a link to the 3DS check.