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

Payment Methods

The following table lists all supported payment methods.

Payment MethodPayment Method Type
AMEXCards
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 Data from External MPINo
3DS RedirectionYesNot supported with Credit requests.
InstallmentsNo
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. For help, see Enabling 3DS. In the PaymentsOS Control Center, register webhooks to be notified when a transaction changes its status.Optional

Enabling 3DS

If you require 3DS, 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

You can use the following Dalenys test cards for testing. Cards with a Dalenys response code starting with 000 return success; all other cards return failure.

Dalenys Response Code Fake PAN
0000 4234603011240000
0001 4234604595740001 (card enrolled for 3DS)
4001 4234607564194001
4002 4234604810334002
4003 4234606735474003
4004 4234609774004004
4005 4234600140624005
4006 4234606214104006
4007 4234609312714007 (not available for Direct VISA/MasterCard accounts)
4010 4234604450614010 (not available for Direct VISA/MasterCard accounts)
4011 4234609939944011
4012 4234604160524012
4013 4234608464714013
5001 4234609090495001
5002 4234604508525002
5003 4234608234385003 (not available for Direct VISA/MasterCard accounts)
5004 4234607483945004

results matching ""

    No results matching ""