Dalenys

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

API Version

Minimum required API version: 1.2.0

The following features require an API version higher than the minimum:

  • 3DS 2.0 External requires API version 1.3.0

Payment Methods

The following table lists all supported payment methods.

Payment MethodPayment Method TypeNotes
American ExpressCardsBoth 3DS 1 external flows and 3DS 2 external flows are not yet supported for American Express.
Carte BancaireCards
MASTERCARDCards
VISACards

Currencies

Over 100 currencies are supported. See currencies.

Features

The following table provides an overview of all supported and non-supported features.

FeatureSupportedNotes
3DS 1.0 ExternalYes
3DS 1.0 InternalYesNot supported with Credit requests.
3DS 2.0 ExternalYes
3DS 2.0 InternalNo
InstallmentsNo
Level 2 and 3 DataNo
Retrieve Supported Payment MethodsNo
Statement Soft DescriptorNo
Stored Credentials FlagYes
Transaction Processing without CVVYes

Requests

The following table lists all supported requests for card-based transactions. Use the bodybuilder to create a sample request body for each request type.

RequestPartial/MultipleModeNotes
AuthorizePartial and multiple are not supportedAsynchronous or SynchronousThe request can be synchronous or asynchronous, depending on whether you implemented a 3DS flow.
Capture Partial is supportedSynchronousPartial and multiple capture depend on your MCC. Contact your Dalenys payment manager for more information.
Charge Not ApplicableAsynchronous or SynchronousThe request can be synchronous or asynchronous, depending on whether you implemented a 3DS flow.
CreditPartial and multiple are not supportedSynchronous
Refund Both partial and multiple are supportedSynchronous
Void Not ApplicableSynchronous

Setup Procedures

The following table lists the configurations that are specific to this integration.

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • identifier: Daleny's processing account technical identifier.
  • apiKey: The account key associated with the account's technical identifier
  • accountCurrency: The currency configured in your Daleny's account.
Required
Enable direct link on your account in order for PaymentsOS be able to make server to server requests on your behalf. Contact Dalenys support for assistance.Required
In your directlink account, allow incoming requests from all IP addresses. Contact Dalenys support for assistance.Required
In your Dalenys account, configure the currency that will be used in transactions initiated on your site. Contact Dalenys support for assistance.Required
In your Dalenys account, enable processing transactions without CVV if desired. Contact Dalenys support for assistance.Optional
In your Dalenys account, enable Credit requests if you want to initiate Credit transactions. Contact Dalenys support for assistance.Optional
In your Dalenys account, configure 3DS Internal 1 if desired. For help, see Enabling 3DS 1 Internal. In the PaymentsOS Control Center, register webhooks to be notified when a transaction changes its status.Optional
If you want to use an external MPI, then you must enable this in your Dalenys account. Beware that using 3DS 2 in external 3DS flow may require additional configuration in your Dalenys account. Contact Dalenys support for assistance. Note: PaymentOS currently does not support using accounts that have been configured to use internal 3DS 2 flows. Using those accounts may cause transactions to fail.Optional

Enabling 3DS 1 Internal

If you require 3DS 1 internal, access your Dalenys account setting and configure the following IPN URLs.

In Transaction notification URL:

In Redirection URL after payment form or 3DSECURE processing:

After configuring the IPN URLs, configure Webhooks in your PaymentsOS environment to receive updates when a change in a transaction status occurs.

As a last step, make sure to include provider_specific_data with an is3ds value of true in your in your Create Authorization or Create Charge API requests:

 "provider_specific_data": {
    "dalenys": {
      "additional_details": {
       ...
        "is3ds": "true"
      }
    }
  },

Note

A 3DS flow will only be executed for cards enrolled for 3DS transactions, even if you pass "is3ds": "true". Payments with cards not enrolled for 3DS will follow a regular (non-3DS) transaction flow.

3DS Response Data

The provided_data.additional_information object returned in the response body of a Create Authorization or Create Charge transaction request will include the following Dalenys-specific data, providing more information about the 3DS transaction flow:

Request Attribute Name Description
Authorize, Charge additional_information.CARD3DSECUREENROLLED Indicates a card's 3DS enrollment status. Can be y (enrolled), n (not enrolled) or u (unknown).
Authorize, Charge additional_information.3DSECURE Indicates whether the transaction included a 3DS authentication step. Either yes orno.

Here's a sample response:

...
{
  "provider_data": {
    ...
    "additional_information": {
      "CARD3DSECUREENROLLED": "y",
      "3DSECURE": "yes"
      ...
    },
  }
},
...

Testing

For test card numbers, see the Dalenys documentation.

results matching ""

    No results matching ""