• Host2Host

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

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.

Once you have set up Google Pay for your account, you can start to accept Google Pay payments.

1. Submit a payment data request to the Google API

   {
     "type": "CARD",
     "parameters": {
       "allowedAuthMethods": ["PAN_ONLY", "CRYPTOGRAM_3DS"],
       "allowedCardNetworks": ["MASTERCARD", "VISA"]
     },
     "tokenizationSpecification": {
       "type": "PAYMENT_GATEWAY",
       "parameters": {
         "gateway": "DECTA",
         "gatewayMerchantId": "<YOUR_MERCHANT_WEBSITE_ID>"
       }
     }
   }
   

   When you submit a payment data request to the Google API, be sure to include the following parameters:

   • gateway: 'DECTA'
   • gatewayMerchantId: '<your merchant website ID>'

   If your DECTA account is set up to process card authorisation requests with AVS checks, you can request BillingAddressParameters in your Google Pay API request (it is advised to request the FULL version of the billing address). If you do not request a billing address through Google Pay, you still have the option to use the address you have on file.

2. Make a request to /orders
   Request example:

{
  //required
  "client":{
  "email": "adam.smith@company.com",
  "address": "Sunny str, 128", // mandatory field for the AVS functionality
  "zip_code": "12 3456" // mandatory field for the AVS functionality
  },
  "products": [
  {
  "quantity": "1",
  "price": "0.30",
  "title": "My Product"
  }
  ],
  //optional
  "currency": "EUR”
}

Response example:

{
  ....
  "api_do_googlepay":"https://gate.decta.com/api/v0.6/pay/a03b5962-1218-4dfd-b78c-1b5ec686ef22/do_googlepay/",
  ....
} 

3. Send the PaymentData you got from the Google Pay API and provide it in your request to DECTA Gate api_do_googlepay endpoint
   Request example:

{
  "signature": "...",
  "intermediateSigningKey": {
  "signedKey": "...",
  "signatures": [...]
  },
  "protocolVersion": "...",
  "signedMessage": "...",
  "ip_address": "127.0.0.1"
}

Response example:

• In case of PAN_ONLY:
  

  {
    "processing_status": "000"
  }
  

• In case of CRYPTOGRAM_3DS:
  

  {
    "threed_check_url":"https://transactions.decta.com/p/a03b5962-1218-4dfd-b78c-1b5ec686ef22/EbbM%252FxU4j8YMDnjAD9qKYTT7%252BcZizmxD51yPZPZj09jTRvePwybnCoOz3Exj%252B%252Bfo8iKX8nP0FdsS1LNBrrXusl%252BPr3rviH38CtLalnRpU38kRRiIU0Qq8TBMQLsXAPreZ8o%252BKYN/3d/"
  }
  

4. Analyze the response:
• In case you receive a processing_status, wait for a webhook about the final status from the DECTA Gate;
• In case you receive a threed_check_url, redirect the shopper to this link to complete the 3D Secure authentication and wait for a webhook about the final status from the DECTA Gate.

• Host2Host
• Full Page
• Embedded Iframe
• Payform Web SDK

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

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.

Full Page and Embedded Iframe

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.

Host2Host

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

1. You as a merchant create an order and as a response you will receive a parameter api_init_paypal;
2. Create a POST request to api_init_paypal endpoint (see the API documentation here) and as a response you will receive a parameter approve_url;
3. Redirect your customer to the approve URL received in the previous step;
4. The customer can now either authorise the PayPal payment or cancel it;
5. If the customer authorises the payment, PayPal will redirect the customer to the return URL;
6. DECTA will proceed either to capturing or holding the payment, according to the merchant’s choice;
7. After 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 Web SDK

• One-Step Payment

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.

Full Page and Embedded Iframe

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.

Host2Host

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

1. You as a merchant create the initial order, and as a response from DECTA you will receive a parameter api_init_volt;
2. Create a POST request to api_init_volt endpoint (see the API documentation API) and as a response you will receive a parameter volt_approve_url;
3. Redirect your customer to the approve URL received in the previous step;
4. The customer can now either authorise the Volt payment or cancel it;
5. If the customer authorises the payment, then Volt will redirect the customer to the return URL;
6. DECTA captures the payment;
7. 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

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*.

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

1. 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 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;
   • In case something goes wrong while DECTA captures the payment, the transaction status will be automatically changed to Failed. If it happens, it is advised for the merchant to wait for a webhook from DECTA Gate side to change the status on their side.

2. 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;
3. Redirect your customer to the approve URL received in the previous step;
4. 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;
5. 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;
6. 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;
7. 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 Web 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.

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.

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

1. 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;

2. 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/"
         }
     

3. As a response you will receive a parameter called openbanking_approve_url;
4. Redirect your customer to the approve URL received in the previous step;
5. The customer can now either authorise the DECTA Open Banking payment or cancel it;
6. 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;
7. After successfully proceeded payment, the payment status is updated for the merchant by DECTA and an appropriate webhook about the status is sent out.