Card payments

Transaction Flows

• iFrame Payment Form
• Full-Page Redirect
• payment.js Integration

Transaction types

• Register / Deregister
• Preauthorize / Capture / Void
• Debit
• Refund
• Recurring Debit/Preauthorize
• Chargebacks

Mandatory Parameters

• customer.identification
• customer.email
• customer.ipAddress

Additional Parameters

• 3D-Secure Verification Parameters

Banco Do Brasil

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.billingAddress1
• customer.billingPostcode
• customer.billingCountry
• customer.email
• customer.nationalId (without special characters)

Additional Parameters

• customer.birthDate

Country and Currency Restrictions

Countries

BR

Currencies

USD

Bancontact

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Country and Currency Restrictions

Countries

BE

Currencies

EUR

Blik

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit & Refund

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Country and Currency Restrictions

Countries

PL

Currencies

PLN

Boleto

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.billingAddress1
• customer.billingPostcode
• customer.billingCountry
• customer.email
• customer.nationalId (without special characters)

Additional Parameters

• customer.birthDate

Country and Currency Restrictions

Countries

BR

Currencies

USD

Bradesco

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.billingAddress1
• customer.billingPostcode
• customer.billingCountry
• customer.email
• customer.nationalId (without special characters)

Additional Parameters

• customer.birthDate

Country and Currency Restrictions

Countries

BR

Currencies

USD

CashtoCode

Transaction Flows

• Full-Page Redirect

Transaction Types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstname
• customer.lastname
• customer.billingCountry
• customer.birthDate

Additional Parameters

none

Country and Currency Restrictions

Countries

AT, DE, IT, UK

Currencies

EUR, GBP

Procedure

A personal URL will be "assigned" to you by CashtoCode which should then be used for the connector configuration hostURL

Coingate

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Additional Parameters

none

DirectCarrierBilling

Transaction Flows

• Redirect (in iFrame)

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry

Additional Parameters

EPS

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Options Request

For EPS you can retrieve the bank list via the Options request identifier epsBankList. You can display this list to your customer in order to pre-select the desired bank.

The result contains a list of banks available for EPS, with BIC code as key and bank name as value. The chosen BIC code of the chosen bank should then be passed as bic element in the IbanCustomer element of the XML.

Country and Currency Restrictions

Countries

AT

Currencies

EUR

Giropay

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• ibanCustomer.billingCountry
• ibanCustomer.firstName
• ibanCustomer.lastName
• ibanCustomer.iban
• ibanCustomer.bic

Additional Parameters

none

Country and Currency Restrictions

Countries

DE

Currencies

EUR

iDeal

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName

Additional Parameters

none

Country and Currency Restrictions

Countries

NL

Currencies

EUR

iSignThis

Transaction Flows

• iFrame Payment Form
• Full-Page Redirect
• payment.js Integration

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.email
• customer.ipAddress

Itau

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.billingAddress1 (for BR)
• customer.billingPostcode (for BR)
• customer.billingCountry
• customer.email
• customer.nationalId (without special characters)

Additional Parameters

• customer.birthDate
• customer.billingAddress1 (for CL)
• customer.billingPostcode (for CL)

Country and Currency Restrictions

Countries

BR, CL

Currencies

USD

Klarna Sofort

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName

Optional Parameters

• customer.bic

Additional Parameters

none

Country and Currency Restrictions

Countries

AT, BE, DE, ES, IT, NL

Currencies

EUR

Multibanco

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Country and Currency Restrictions

Countries

PT

Currencies

EUR

MyBank

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Country and Currency Restrictions

Countries

IT, BE, PT, ES

Currencies

EUR

Neteller

To fully set up the Neteller Connector you will have to fulfill the following (mandatory) steps:

• Enter your Private Key Username & Private Key Password in the "Extra Data" Fields. (Merchants / User / Connectors / Neteller / Config / Extra Data).
  • You can retrieve your Private and Public keys via the Neteller Merchant Dashboard (Developer / Apps; You might need to "Add application")
  • Copy the Username & Password from the Section "PRIVATE Key".
• Inform Paysafe ([email protected]) to set up your Webhook URL.
  • You can retrieve your Webhook URL via the Connector Settings (Merchants / User / Connectors / Neteller / Base Data / Notification Url).
  • Send them the given "Notification URL".

Payment Methods

Additional Parameters

PayPal

Payment Methods

PayPal Payment Types

PayPal supports different kind of payments:

• Sale: Will charge the user for the full amount of the transaction
• Authorization: Only authorizes the user's payment instrument. This needs afterwards to be captured with a Capture request
• Order: Only gets consent from user for this particular order. No funds will be authorized

A Debit will always use the Sale type. A Preauthorize will by default use the Authorization type.

You can control the behavior for Preauthorize by sending the paypalPaymentAction parameter (see below).

Additional Parameters

You can use the following extraData keys, which will be passed in the corresponding fields to PayPal:

Items

If submitting items, the following fields are Mandatory:

Item ExtraData Parameters:

PayPal Complete Platform

Payment Methods

Integration guide

PayPal

PayPal requires you to display the PayPal Button on your Checkout page. This is handled by the payment.js integration.

​1. Embed the payment.min.js in your page

<script data-main="payment-js" src="https://gateway.dimoco-payments.eu/js/integrated/payment.1.3.min.js"></script>

​2. Provide a DIV element on your page for the PayPal button

<div id='paypalButtonDiv'></div>

​3. Initialize the payment.js with the following parameters:

• ID of the DIV element
• Javascript function to handle payment completion
• Javascript function to handle error events
• Javascript function to handle cancellation events
• PayPal options (see below in example, refer to PayPal Documentation for possible options. The 'vault' option is per default set to 'false' if not otherwise specified. Please refer to the PayPal Documentation for the different button options)
• Your server endpoint where prepareCall is implemented. It could either be prepare-debit/prepare-preauthorize/prepare-register based on the transaction type

PayPal options

<script>
  var paymentJs = new PaymentJs('1.3');

  errorHandler = function (error) {
      // If an error prevents buyer checkout, alert the user that an error has occurred with the buttons using the onError callback
  }

  cancellationHandler = function (data) {
      // When a buyer cancels a payment, they typically return to the parent page.
      // You can instead use the onCancel function to show a cancellation page or return to the shopping cart.
  }

  completeHandler = function (paypalToken) {
      // Captures the funds from the transaction and shows a message that tells the buyer the payment was successful.
      // The method is called after the buyer approves the transaction on the paypal.com website.
      // paypalToken should be passed to the debit request using extraData with the key 'paypalToken'

  }

  var paypalOptions = {
      button: {
          color: gold,
      },
      currency: "EUR",
      intent: "capture" || "authorize", // debit = capture / preauthorize = authorize
      vaultingWithoutPurchase: false, // should be set to true if you're doing register call
      vault: false, // should be set to true if you would like to vault transaction using PayPal vaulting. for example register / debit + withRegister=true
      locale: 'en_US', // override PayPals default language detection
      fraudNetCmid: 'YOUR_32_CHAR_CMID', // only when FraudNet is enabled - see FraudNet
      fraudNet: {                        // optional FraudNet tuning
          mm: true,
      },
  };

  // Prepare Transaction
  var prepareCall = () => {
    return fetch('{MY_PREPARE_ENDPOINT}', {
      method: 'POST',
    }).then(function (res) {
      return res.json();
    }).then(function (data) {
      return data.orderID;
    });
  };

  paymentJs.initPaypal(
    'public-integration-key',
    'paypal-button-div',
    completeHandler,
    errorHandler,
    cancellationHandler,
    paypalOptions,
    prepareCall
  );
</script>

​4. You can now call the Transaction API with the extraData.paypalToken set to the paypalToken returned to the completeHandler.

Prepare Transaction

PayPal requires to create order/setup token when the PayPal button is being pressed. That's being handled with prepare-debit/prepare-preauthorize/prepare-register API calls. Therefore, you would need to implement prepareDebit call and provide your server endpoint initializing PayPal via PaymentJs.

When using the Hosted Payment Page option, the prepare call can be handled automatically on our side. E.g.

 prepareCall = function() {
    return fetch('', {
        method: 'POST',
        headers: {
            'Accept': 'application/json',
            'Content-Type': 'application/json'
        }
    }).then(function (res) {
        return res.json();
    }).then(function (data) {
        return data.orderID;
    });
}

Additional Prepare Transaction Parameters (CreateOrder)

Permit multiple payment tokens

When vaulting a PayPal account, PayPal by default refuses to create a second payment token for a PayPal account that is already vaulted with the same merchant, and returns the existing token instead. Setting permit_multiple_payment_tokens to true allows PayPal to create an additional, independent payment token for that same account.

The default is configured on the connector. To overwrite it for a single transaction, send extraData.permit_multiple_payment_tokens with "true" or "false" — the transaction value always takes precedence over the connector setting.

This applies to both vaulting flows:

Example API Request:

{
  "extraData": {
    "paypalToken": "the token returned to your completeHandler",
    "permit_multiple_payment_tokens": "true"
  },
  "withRegister": true
}

One-click payment / Customer Initiated Transaction

To render One-click payment button you would need to do a prepareDebit/preparePreauthorize call to retrieve user-token-id that needs to be passed to paymentJs via paypalOptions.userIdToken.

Example API Request:

{
  "referenceUuid": "referenceUuid",
  "extraData": {
    "useReturnUserExperience": "true"
  },
  "transactionIndicator": "CARDONFILE"
}

Example API Response:

{
  "data": {
    "success": true,
    "returnType": "FINISHED",
    "widgetToken": "eyJraWQiOiJhMDRiMjEwZDYzYjU0NWQzODEwOWUxNDM3ZjQ3ZWYxMiIsInR5cCI6IkpXVCIsImFsZyI6IkVTMjU2In0.eyJpc3MiOiJodHRwczovL2FwaS5zYW3kYm94LasdasXBhbC5jb20iLCJzdWIiOiJDRVlINFVNUUpLMzM4IiwiYWNyIjpbImNsaWVudCJdLCJzY29wZSI6WyJCcmFpbnRyZWU6VmF1bHQiXSwib3B0aW9ucyI6eyJjdXN0b21lcl9pZCI6IklpUklSYWR1UEMifSwiYXoiOiJjY2cxOC5zbGMiLCJleHRlcm5hbF9pZCI6WyJQYXlQYWw6Q0VZSDRVTVFKSzMzOCIsIkJyYWludHJlZTozZG04NjdjdHJyZ3Y2Y2R3Il0sImV4cCI6MTcxNTcwNTEwNiwiaWF0IjoxNzE1NzA0MjA2LCJqdGkiOiJVMkFBSVA4NGprc3dfX1pYSHduR21KeVRQV003SkxzbFJLVlI2OHlxOEN4YmhHN1VWNkFWVVlyTTBqbXRyVEZmU3hBbjZKa0hlekNvSUtTdlZ6LUVpR1JxbVl4VWZaRHJOMDY1eXZQRkMySmgtQWkxaXNiV0xOWnh1MWJNa0VkdyJ9._s54YCC8MRqjllX2wDTmo4fQyTkUXl6_7aPOiNwBnVBJfLoQlwIZvtrkvgxU7RPBQy3uiRp-hhK4LGvwRC74CA"
  }
}

Items

If submitting items, the following fields are Mandatory:

Item Additional Parameters:

Additional Postback ExtraData

PayPal ACDC

​1. Embed the payment.min.js in your page

<script data-main="payment-js" src="https://gateway.dimoco-payments.eu/js/integrated/payment.1.3.min.js"></script>

​2. Provide an input field for the paypalToken which will be created later.

<input type="hidden" name="paypalToken" id="paypalToken" value="">

​3. Initialize the payment.js with the following parameters:

paymentJsPayPal.initPaypal(
  'the public integration key of your connector',
  {
    cardName: 'card-name-field-container',
    cardNumber: 'card-number-field-container',
    cardCvv: 'card-cvv-field-container',
    cardExpiry: 'card-expiry-field-container'
  },
  completeHandler,     <!-- your callback function for when the token has been created -->
  errorHandler,        <!-- your callback function in case of error -->
  cancellationHandler, <!-- your callback funciton in case of cancellation -->
  payPalOptions,       <!-- see PayPalOptions -->
  prepareCall          <!-- see prepareCall -->
);

completeHandler

The completeHandler callback will be called once the PayPal token has been created

Example

completeHandler = function (payPalToken) {
    // do things when the PayPal token is created
    console.log('done: ' + payPalToken);

    // set the PayPal token and submit
    <!-- important to name it paypalToken -->
    document.getElementById("paypalToken").value = paypalToken;
    document.getElementById("payment-form").submit();
}

prepareCall

The prepareCall must be implemented by you and is based on the transaction type: prepare-debit/prepare-preauthorize/prepare-register

Please refer to Prepare Transaction

When using the Hosted Payment Page option, the prepare call can be handled automatically on our side. E.g.

  prepareCall = function() {
      document.getElementById('loader').style.display = '';

      return fetch('{{ paypal.prepareCallEndpoint }}', {
          method: 'POST',
      }).then(function (res) {
          return res.json();
      }).then(function (data) {
          return data.orderID;
      });
  }

errorHandler, cancellationHandler

Here you may implement handling of scenarios for errors and user cancellations.

payPalOptions

Example

var paypalOptions = {
      currency: "EUR",
      intent: "authorize",
      vaultingWithoutPurchase: false,
      vault: false,
      style: {
          'input': {
              'font-size': '12px',
              'line-height': '1.7rem',
              'color': '#000',
              'padding': '5px',
              'appearance': 'none'
          },
          ':focus': {
              'padding': '5px',
              'outline': 'none'
          }
     }
};

​4. Trigger Payment with billing address data

Billing address data should be collected and submitted with the card data.

To trigger the payment you may use the paymentjs.trigger(data) function.

Example

document.getElementById('submit-btn').addEventListener('click', function (event) {
  event.preventDefault();
  paymentJs.trigger({
    billingAddress: {
      addressLine1: document.getElementById('card-billing-address-line-1').value,
      addressLine2: document.getElementById('card-billing-address-line-2').value,
      adminArea1: document.getElementById('card-billing-address-admin-area-line-1').value,
      adminArea2: document.getElementById('card-billing-address-admin-area-line-2').value,
      countryCode: document.getElementById('card-billing-address-country-code').value,
      postalCode: document.getElementById('card-billing-address-postal-code').value
    }
  });
});

Please note that billing address line 1 and country code are mandatory.

Content Security Policy Nonce

If your checkout page is served with a strict Content-Security-Policy that does not allow 'unsafe-inline', the PayPal SDK needs the nonce of your page to be able to inject its own inline scripts and styles. PayPal reads that nonce from a data-csp-nonce attribute on its SDK script tag — see PayPal: using a nonce instead of unsafe-inline.

Because the SDK script tag is created by payment.js and not by you, the nonce has to be handed over via the sdk.dataAttributes option of paypalOptions. Every key/value pair given there is set as an attribute on the SDK script tag, so csp-nonce ends up as data-csp-nonce.

Example

var paypalOptions = {
    currency: "EUR",
    intent: "capture",
    sdk: {
        dataAttributes: {
            'csp-nonce': 'THE_NONCE_OF_YOUR_PAGE'
        }
    }
};

Set Transaction Context

FraudNet

FraudNet is PayPal's browser-based device data collection. When enabled, the PayPal connector JavaScript loads PayPal's FraudNet script on the checkout page, and a client metadata id (CMID) is sent when the order is created, authorized and captured, in the PayPal-Client-Metadata-Id header. PayPal correlates the two.

fraudNetSourceWebsiteId is yours to define. PayPal recommends <MERCHANT_NAME>_<PAGE_NAME>, at most 32 characters, and requires a different identifier for each page you integrate FraudNet on.

Connector configuration

Hosted Payment Page

A new CMID is generated for you on every page load, as PayPal requires, and exposed to your payment template. Forward it into the PayPal options:

var paypalOptions = {
    fraudNetCmid: "",
    // ...your other options
};

Until your template is updated, FraudNet stays inactive — no script is loaded and no CMID is sent. Nothing else about the payment page changes.

Your own checkout (payment.js)

Generate a 32-character alphanumeric CMID yourself — a new one each time the checkout page is loaded — send it on the transaction as extraData.paypal_cmid, and pass the same value to initPaypal:

paymentJs.initPaypal(
    'public-integration-key',
    'paypal-button-div',
    completeHandler,
    errorHandler,
    cancellationHandler,
    { fraudNetCmid: yourCmid, /* ...your other options */ },
    prepareCall
);

Both values must be identical. If they differ, PayPal receives device data it cannot associate with the transaction, and no error is reported.

Optional parameters

Pass any of these in the fraudNet option object:

Example:

var paypalOptions = {
    fraudNetCmid: "",
    fraudNet: {
        mm: true,
        ts: { type: 'CARD', fields: ['card-number'] },
    },
};

Not supported: f, s and sandbox are set by us and cannot be overridden — f must match the CMID sent in the API header, s comes from your connector configuration, and sandbox follows the connector's test mode. b (custom beacon endpoint) is not passed through. cb1 and cb2 are not supported, because the FraudNet parameter block is JSON and cannot carry function values.

Timing

FraudNet is loaded when initPaypal is called. Call it on page load rather than deferring it until the shopper selects PayPal, so FraudNet has the whole checkout session to collect data.

Native apps

We do not provide a mobile SDK, so PayPal Magnes cannot be integrated on our side. If your own app integrates Magnes, send the CMID it generates as extraData.paypal_cmid and it is forwarded to PayPal. Values that are not 32 alphanumeric characters are ignored.

This requires enableFraudNet on the connector — it gates the header as well as the browser snippet. You do not need fraudNetSourceWebsiteId for this, since no page of ours is rendered; without the flag the CMID you send is dropped silently.

This applies to flows where we do not render the payment page. If your shopper is sent to our hosted payment page, that page generates its own CMID and overwrites the one you sent — FraudNet fires from our page, so a value you supplied would correspond to no collected data.

FraudNet is unrelated to the Fraud.net external risk check, which is configured as a risk rule rather than a connector setting.

Paysafecard

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit
• Refund

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Country and Currency Restrictions

Countries

AT, AU, BE, BG, CA, CH, CY, CZ, DE, DK, ES, FI, FR, GB, GE, GI, GR, HR, HU, IE, IT, LI, LT, LU, MT, MX, NL, NZ, NO, PE, PL, PT, RO, SE, SI, SK, UY

Currencies

ARS, AUD, BRL, CAD, CHF, CZK, DKK, EUR, EGP, GBP, HRK, HUF, KWD, MXN, NZD, NOK, PEN, PLN, RON, SEK, TRY, USD, UYU, VAE

PayU

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit & Refund

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Optional Parameters

• customer.email

Additional Parameters

none

Country and Currency Restrictions

Countries

PL, CZ

Currencies

PLN, CZK

SEPA Direct Debit

Transaction Flows

• Server-to-Server

Transaction types

• Debit
• Recurring Debit
• Refund
• Chargeback

Mandatory Parameters

• description
• additionalId1 (should contain your Purchase Order ID)
• additionalId2 (only for recurring transaction, should contain your Contract ID)
• ibanCustomer.firstName
• ibanCustomer.lastName
• ibanCustomer.iban
• ibanCustomer.mandateDate
• ibanCustomer.mandateId

Additional Parameters

none

Country and Currency Restrictions

Countries

All SEPA countries

FI, AT, BE, BG, ES, HR, CY, CZ, DK, EE, FI, FR, GF, DE, GI,
GR, GP, HU, IS, IE, IT, LV, LI, LT, LU, MT, MQ, YT, MC, NL,
NO, PL, PT, RE, RO, BL, MF, PM, SK, SI, ES, SE, CH, GB

Currencies

EUR

SEPA Direct Debit PLUS

Transaction Flows

• iFrame or Full-Page Redirect

Transaction types

• Register
• Debit
• Recurring Debit
• Refund
• Chargeback

Mandatory Parameters

• description
• additionalId1 (should contain your Purchase Order ID)
• additionalId2 (only for recurring transaction, should contain your Contract ID)
• customer.firstName
• customer.lastName

Additional Parameters

For Register transactions:

• extraData.checkAmount (e.g. 9.99)
• extraData.checkCurrency (e.g. "EUR")

Providing these data fields, the system automatically verifies on the customer's bank account if the required balance is available. In case the balance is lower than the required amount, the Register transaction will fail with an Insufficient funds error.

Country and Currency Restrictions

Countries

All SEPA countries

FI, AT, BE, BG, ES, HR, CY, CZ, DK, EE, FI, FR, GF, DE, GI,
GR, GP, HU, IS, IE, IT, LV, LI, LT, LU, MT, MQ, YT, MC, NL,
NO, PL, PT, RE, RO, BL, MF, PM, SK, SI, ES, SE, CH, GB

Currencies

EUR

SEPA Credit Transfer

Transaction Flows

• Server-to-Server

Transaction types

• Payout

Mandatory Parameters

• description
• additionalId1 (should contain your Credit Statement ID)
• ibanCustomer.firstName
• ibanCustomer.lastName
• ibanCustomer.iban
• ibanCustomer.mandateDate
• ibanCustomer.mandateId

Additional Parameters

none

Country and Currency Restrictions

Countries

All SEPA countries

FI, AT, BE, BG, ES, HR, CY, CZ, DK, EE, FI, FR, GF, DE, GI,
GR, GP, HU, IS, IE, IT, LV, LI, LT, LU, MT, MQ, YT, MC, NL,
NO, PL, PT, RE, RO, BL, MF, PM, SK, SI, ES, SE, CH, GB

Currencies

EUR

Rapi Pago

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.billingCountry
• customer.email
• customer.nationalId (without special characters)

Additional Parameters

• customer.birthDate
• customer.billingAddress1
• customer.billingPostcode

Country and Currency Restrictions

Countries

AR

Currencies

USD

Skrill

Transaction Flows

• Full-Page Redirect

Transaction types

Debit

Payout

Refund

Partial refund is supported.

Trustly

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit & Refund

Mandatory Parameters

• customer.identification
• customer.billingCountry
• customer.firstName
• customer.lastName
• customer.email
• description

Optional Parameters

• customer.ipAddress
• customer.nationalId (without special characters)

Additional Parameters

none

Country and Currency Restrictions

Countries

AT, DE, DK, EE, FI, GB, LT, LV, NL, NO, SE

Currencies

DKK, EUR, GBP, NOK, SEK

TrustPay

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName

Additional Parameters

none

Country and Currency Restrictions

Countries

CZ, SK

Currencies

CZK, EUR

Pago Facil

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.identification
• customer.firstName
• customer.lastName
• customer.billingCountry
• customer.email
• customer.nationalId (without special characters)

Additional Parameters

• customer.birthDate
• customer.billingAddress1
• customer.billingPostcode

Country and Currency Restrictions

Countries

AR

Currencies

USD

Przelewy24

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.email
• customer.billingCountry
• customer.firstName
• customer.lastName
• description

Additional Parameters

none

Country and Currency Restrictions

Countries

PL

Currencies

PLN, EUR

Qiwi Wallet

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit, Refund

Mandatory Parameters

• description
• successUrl
• callbackUrl
• customer.firstName
• customer.lastName
• customer.billingCountry
• customer.billingPhone

Additional Parameters

none

Country and Currency Restrictions

Countries

RU, KZ, UA

Currencies

EUR, KZT, RUB, USD

Verkkopankki (Finnish Online-Bank Transfer)

Transaction Flows

• Full-Page Redirect

Transaction types

• Debit

Mandatory Parameters

• customer.billingCountry
• customer.firstName
• customer.lastName

Additional Parameters

none

Country and Currency Restrictions

Countries

FI

Currencies

EUR

Wirecard

Transaction Flows

• iFrame Payment Form
• Full-Page Redirect
• payment.js Integration

Transaction types

• Debit
• Register
• Preauthorize
• Capture
• Void
• Refund
• Deregister

Mandatory Parameters

none

Additional Parameters

none

Risk-Check Only

For this kind of connector you submit a transaction just like a normal transaction, but in fact no real money flow will occur.

The result tells you whether this transaction has passed the risk checks or not. (SUCCESS or ERROR with code 2013)

Transaction Flows

• Server-to-Server

Transaction types

• Debit
• Preauthorize

Mandatory Parameters

The mandatory parameters depend on your individual merchant configuration

Additional Parameters

none

Restricted Countries for all payment methods

• Afghanistan
• Iran
• Sudan South
• Belarus
• Iraq
• Syria
• Burundi
• Korea (North)
• Trinidad & Tobago
• Bosnia & Herzegowina
• Laos
• Tunisia
• Central African Republic
• Lebanon
• Uganda
• Crimea
• Libya
• Vanuatu
• Cuba
• Nicaragua
• Yemenia
• Darfur
• Somalia
• Zimbabwe
• Democratic Republic Congo
• Sri Lanka
• Guyana
• Sudan