S-money API

Method of integrating the registraton form

Thibault Bargat — 2020-03-10T11:43:49Z

Principle:

1. You display a payment page including a registration form, except that the bankcard input fields are replaced by hosted-fields containers. These containers could be any HTML tag: div, p, span… the hosted-fields JavaScript library injects Dalenys-hosted iframes in these containers, each containing the card data input fields
2. At the submit process, you should call the createToken method of the hosted-fields library which will trigger the tokenization of the cardholder data (card number, expiry date and cryptogram)
3. If the tokenization is successful, you must add the received token to your form submission request (e.g. by adding a hidden input)

Creation of the form:

You must own a TLS certificate to host a valid HTTPS payment page, otherwise the user's browser will display security alerts and is likely to block it.
The hosted-fields library must always be called online. Using a downloaded version hosted on your own server can cause serious malfunctions, especially in the case of an update of the API.

1- First of all, you must include the Dalenys hosted-fields dedicated library, by adding the following code between the and tags in your HTML:
•

The identifiers used in the script to designate the fields are those used for the identifiers of the containers created in the form. This allow the script to inject the fields hosted by Dalenys in these containers.

5- Load the hosted fields library

At this point, your web browser may display the bank card input fields into their containers.

6- Token generation
Once the user submits the form, you should call the createToken method to trigger the tokenization process.
This method expects a callback in parameter which will be triggered once the tokenization request is finished.
Your callback will receive a result object containing these properties:
execCode: The technical result code of the tokenization call. In case of success, 0000 will be sent
message: The description linked to the execCode
cardType: The card type
cardCode: The first 6 and last 4 digits of the cardholder's card number
cardValidityDate: Card expiry date
selectedBrand: Cardholder selected brand in case of co-branded card.
hfToken: Of course the generated token

In case of success you have to add the received token to the form submit request (by adding an hidden input for example) :

7- Include EXTRADATA property (from the result of the call to create the card payment) in hidden fields:

Registration with 3d secure Authentication

Depending on the card used during the payment, the submission of the registration form, a 3DSecure authentication may be necessary.
In this case, the HTML page of the 3DSecure form is sent in response content with a http status code 200 (OK).
The submission of the 3DSecure form will end with a 302 redirection to the url entered in the urlReturn field of the initial request.

Retrieve a bank card

Thibault Bargat — 2020-03-10T11:20:53Z

Headers :
GET /api/ domainePartenaire/cards/registrations/appcardid
Accept : application/vnd.s-money.v3+json
Content-Type : application/vnd.s-money.v3+json
Authorization : Bearer ACCESS_TOKEN

Response :

HTTP/1.1 200 OK

{ 
 "AuthorizationAmount":0,
 "Card":{ 
 "Id":1418,
 "AppCardId":"carte22",
 "Network":1,
 "Hint":"423460XXXXXX0000",
 "Name":"my card",
 "Country":"FR",
 "ExpiryDate":"2022-12-31T23:59:59"
 },
 "Status":1,
 "ThreeDsecurePreference":0,
 "UrlReturn":"http://s-money.fr/urlReturn",
 "UrlCallback":"https://url-de-callback-client",
 "AvailableCards":"CB",
 "ErrorCode":0,
 "ExtraResults":{ 
 "threedsecure":"true",
 "threedsecureauthstatus":"y",
 "threedsecuresignaturestatus":"y",
 "threedsecureglobalstatus":"ok",
 "ThreeDsCardEnrolled":"y",
 "ExecCode":"0000",
 "ExecMessage":"Successful operation",
 "warrantyResult":true,
 "3dsecureVersion":2,
 "3dsecureMode":1,
 "bankauthResult":0
 },
 "extraparameters":{ 
 "profilename":"3DSV2"
 }

}

Add a bank card

Thibault Bargat — 2020-03-09T16:52:09Z

Headers :
POST /api/cards/registrations
Accept : application/vnd.s-money.v3+json
Content-Type : application/vnd.s-money.v3+json
Authorization : Bearer ACCESS_TOKEN

Request :

{ 
 "ThreeDsecurePreference":0,
 "card":{ 
 "appcardid":"carte22",
 "name":"my card"
 },
 "availableCards":"CB",
 "holder":{ 
 "name":"Jean Dupont",
 "mail":"Jean.dupont@email.fr"
 },
 "extraparameters":{ 
 "profilename":"3DSV2"
 },
 "AuthorizationAmount":0,
 "urlReturn":"http://s-money.fr/urlReturn",
 "urlCallback":"https://url-de-callback-client",
 "Billing":{ 
 "City":"Paris",
 "Country":"FR",
 "Address":"1 rue de paris",
 "PostalCode":"75001",
 "Billingaddressstate":"california"
 },
 "ShipTo":{ 
 "City":"Paris",
 "Country":"FR",
 "Address":"1 rue de paris",
 "PostalCode":"75001",
 "AddressType":0,
 "AddressState":"california",
 "AddressDate":"2018-01-10"
 },
 "Delivery":{ 
 "email":"pierre@dupont.fr",
 "timeframe":"sameday"
 },
 "ClientScreen":{ 
 "ColorDepth":32, 
 "ScreenHeight":1280,
 "ScreenWidth":1024
 },
 "ThreeDsOptData":{ 
 "AccountChangeDate":"2018-01-10",
 "AccountCreationDate":"2018-01-10",
 "ClientAuthMethod":"guest",
 "Passwordchangedate":"2018-01-10",
 "Last6MonthsPurchaseCount":4,
 "Last24hoursaddcardattempts":2,
 "Last24hourstransactioncount":4,
 "Last12Monthstransactioncount":4,
 "Cardenrolldate":"2018-01-01",
 "Suspiciousaccountactivity":false,
 "Homephone":"+33133333333",
 "Mobilephone":"+33633333333",
 "Workphone":"+33633333333",
 "Giftcard":{ 
 "Amount ":"100",
 "Count":"2",
 "Currency":"EUR"
 },
 "Preorderdate":"2020-01-04",
 "Itemavailability":true,
 "Reorderingitem":false,
 "Recurringexpiry":"2020-01-04",
 "recurringfrequency":10
 }

}

Response
HTTP/1.1 201 CREATED
Location: /api/domainePartenaire/cards/registrations/card123

{ 

HTTP/1.1 201 CREATED

{ 
 "ExtraData":"{\"IsSchedule\":false,\"IsCardRegistration\":false,\"Profile\":\"hostedfields\",\"UrlReturn\":\"http%253A%252F%252Fwww.google.fr\",\"Cards\":null,\"FormIntegrationMode\":0}",
 "Holder":{ 
 "Name":"Jean Dupont",
 "Mail":"Jean.dupont@email.fr"
 },
 "AuthorizationAmount":0,
 "Card":{ 
 "Id":1418,
 "AppCardId":"carte22",
 "Network":null,
 "Hint":null,
 "Name":"my card",
 "Country":null,
 "ExpiryDate":null
 },
 "Status":1,
 "ThreeDsecurePreference":0,
 "UrlReturn":"http://s-money.fr/urlReturn",
 "UrlCallback":"https://url-de-callback-client",
 "AvailableCards":"CB",
 "ErrorCode":0,
 "ExtraResults":{ 
 "threedsecure":null,
 "threedsecureauthstatus":null,
 "threedsecuresignaturestatus":null,
 "threedsecureglobalstatus":null,
 "ThreeDsCardEnrolled":null,
 "ExecCode":"0000",
 "ExecMessage":"Successful operation",
 "warrantyResult":true,
 "3dsecureVersion":2,
 "3dsecureMode":null,
 "bankauthResult":null
 },
 "extraparameters":{ 
 "profilename":"3DSV2"
 },
 "Billing":{ 
 "City":"Paris",
 "Country":"FR",
 "Address":"1 rue de paris",
 "PostalCode":"75001",
 "Billingaddressstate":"california "
 },
 "ShipTo":{ 
 "City":"Paris",
 "Country":"FR",
 "Address":"1 rue de paris",
 "PostalCode":"75001",
 "AddressType":0,
 "AddressState":"california ",
 "AddressDate":"2018-01-10"
 },
 "Delivery":{ 
 "email":"pierre@dupont.fr",
 "timeframe":"sameday"
 },
 "ClientScreen":{ 
 "ColorDepth":32, 
 "ScreenHeight":1280,
 "ScreenWidth":1024
 },
 "ThreeDsOptData":{ 
 "AccountChangeDate":"2018-01-10",
 "AccountCreationDate":"2018-01-10",
 "ClientAuthMethod":"guest",
 "Passwordchangedate":"2018-01-10",
 "Last6MonthsPurchaseCount":4,
 "Last24hoursaddcardattempts":2,
 "Last24hourstransactioncount":4,
 "Last12Monthstransactioncount":4,
 "Cardenrolldate":"2018-01-01",
 "Suspiciousaccountactivity":false,
 "Homephone":"+33133333333",
 "Mobilephone":"+33633333333",
 "Workphone":"+33633333333",
 "Giftcard":{ 
 "Amount ":"100",
 "Count":"2",
 "Currency":"EUR"
 },
 "Preorderdate":"2020-01-04",
 "Itemavailability":true,
 "Reorderingitem":false,
 "Recurringexpiry":"2020-01-04",
 "recurringfrequency":10
 }

}

Resources

Thibault Bargat — 2020-03-09T13:59:47Z

1.CardRegistration

Property	Type	Mandatory	Description
ThreeDSecurePreference	Int	O	0 = ask for a strong authentication 1 = ask for a frictionless authentication 2 = ask for no preference, the decision will be made by issuer; 3 = ask for no authentication
availableCards	String	O	List of cards to be displayed on the registration page. Possible values ( to separate with ' ;' ) : CB MASTERCARD MAESTRO VISA VISA_ELECTRON
AuthorizationAmount	Int	N	Deux valeurs possibles (en centimes): • 0 • 100 (1€)
urlReturn	String	O	Url of callback client requested at the end of a card registration
urlCallback	String	O	Specify url of callback server requested at the end of adding card (the domain must be the same as the one of the callback URL provided initially)
Status	Int	O	Status of the card registration 0 = Waiting 1 = Completed 2 = Failed
ErrorCode	Int	O	0 = 0XXX operation succeeded or still processing 10 = 1XXX operation rejected because of bad request configuration 11 = 2XXX operation rejected because of bad reference usage 12 = 3XXX operation rejected because of bad account configuration 13 = 4XXX operation rejected because of the bank or the supplier 14 = 5XXX operation rejected because of a system error 15 = 6XXX operation rejected because of anti-fraud engine
Extradata	String	/	ExtraData to be included in card registration form into :

2.Card

Property	Type	Mandatory	Description
Id	Long	/	Card ID
AppCardId	String	O	Card identifier in the third-party application
Network	Long	/	UNKNOWN = -1, CB = 1, MASTERCARD = 2, VISA = 3,
Hint	String	/	Hide the card number. 6XXXX4 format
Name	String	O	Card name
Country	String	/	ISO country code of the card
ExpiryDate	Date	/	Card expiration date

3.Holder

Property	Type	Mandatory	Description
Name	String	O	The holder's full name (as described on the payment method).
mail	String	O	The user's email.

4.Extraparameters

Property	Type	Mandatory	Description
ProfilName	String	O	Value “3DSV2” to call 3D-Secure 2.0 By default, without profil, 3DS V1 will be called

5.Billing

Property	Type	Mandatory	Description
City	String	O	The billing city.
Country	String	O	The country code (ISO_3166-1_alpha-2).
Address	String	O	The billing address. Be careful not to integrate any line breaks.
PostalCode	String	O	The billing postal code.
Billingaddressstate	String	N	The billing address state.

6.ShipTo

Property	Type	Mandatory	Description
City	String	O*	The shipping city. Mandatory if AdresseType is not EDELIVERY
Country	String	O*	The country code (ISO_3166-1_alpha-2 format) Mandatory if AdresseType is not EDELIVERY
Address	String	O*	The shipping address. Mandatory if AdresseType is not EDELIVERY
PostalCode	String	O*	The shipping postal code. Mandatory if AdresseType is not EDELIVERY
AddressType	Int	O	Shipping indicator. 0 = eDelivery 1 = Verified 2 = New 3 = Billing 4 = Store Pickup 5 = Travel Pickup 6 = Other The parameter DELIVERYEMAIL is mandatory when EDELIVERY mode is set. The other ship to address fields are optional when ‘storepickup', travelpickup or other is set.
AddressState	String	N	The shipping address state.
AddressDate	String	N	Date when the shipping address used for this transaction was first used with the 3DS Requestor.

7.Delivery

Property	Type	Mandatory	Description
email	String	O*	Mandatory if ShipToAddressType value is eDelivery For Electronic delivery, the email address to which the merchandise was delivered.
timeframe	String	N	Possible values : electronic, sameday, overnight, longer

8.ClientScreen

Property	Type	Mandatory	Description
ColorDepth	Int	O	Value representing the bit depth of the colour palette for displaying images, in bits per pixel. Obtained from Cardholder browser using the screen.colorDepth property. Ex : 32
ScreenHeight	Int	O	Total height of the Cardholder's screen in pixels. Value is returned from the screen.height property. Ex : 1280
ScreenWidth	Int	O	Total width of the cardholder's screen in pixels. Value is returned from the screen.width property. Ex : 1024

9.ThreeDsOptData

Property	Type	Mandatory	Description
ClientAuthMethod	String	N	guest: No merchant authentication occurred (i.e. cardholder “logged in” as guest); credentials: Login to the cardholder account at the merchant system using merchant's own credentials; federated: Login to the cardholder account at the merchant system using federated ID; issuer: Login to the cardholder account at the merchant system using issuer credentials; thirdparty: Login to the cardholder account at the merchant system using third-party authentication; fido: Login to the cardholder account at the merchant system using FIDO Authenticator;
AccountChangeDate	Date	N	Date that the cardholder's account with the 3DS Requestor was last changed, including Billing or Shipping address, new payment account, or new user(s) added.
AccountCreationDate	Date	N	Date that the cardholder opened the account with the 3DS Requestor.
Passwordchangedate	Date	N	Date that cardholder's account with the 3DS Requestor had a password change or account reset.
Last6MonthsPurchaseCount	Int	N	Number of purchases with this cardholder account during the previous six months.
Last24hoursaddcardattempts	Int	N	Number of “Add Card” attempts in the last 24 hours.
Last24hourstransactioncount	Int	N	Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous 24 hours.
Last12Monthstransactioncount	Int	N	Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous year.
Cardenrolldate	date	N	Date that the payment account was enrolled in the cardholder's account with the 3DS Requestor.
Suspiciousaccountactivity	Boolean	N	Indicates whether the 3DS Requestor has experienced suspicious activity (including previous fraud) on the cardholder account.
Homephone	string(max 32)	N	The home phone number provided by the Cardholder in international (E.164) format.
Mobilephone	string(max 32)	N	The mobile phone number provided by the Cardholder in international (E.164) format.
Workphone	string(max 32)	N	The work phone number provided by the Cardholder in international (E.164) format.
Preorderdate	date	N	For a pre-ordered purchase, the expected date that the merchandise will be available.
Itemavailability	Boolean	N	Indicates whether Cardholder is placing an order for merchandise with a future availability or release date.
Reorderingitem	Boolean	N	Indicates whether the cardholder is reordering previously purchased merchandise.
Recurringexpiry	date	N	Date after which no further authorisations shall be performed in a recurring payment workwlow.
recurringfrequency	Int	N	Indicates the minimum number of days between authorisations. Ex : 10

10.GiftCard

Property	Type	Mandatory	Description
Amount	Int	N	For prepaid or gift card purchase, the purchase amount total of prepaid or gift card(s) in minor units (cents).
Count	Int	N	For prepaid or gift card purchase, total count of individual prepaid or gift cards/codes purchased.
Currency	String	N	For prepaid or gift card purchase, the currency code of the card as defined in ISO 4217.

11.ExtraResults

Property	Type	Mandatory	Description
threedsecure	Boolean	/	True / False
threedsecureauthstatus	Int	/	0 = Yes 1 = No 2 = unavaible 3 = Attempted
threedsecuresignaturestatus	Int	/	0 = Yes 1 = No
threedsecureglobalstatus	Int	/	0 = Yes 1 = Not_enrolled 2 = unavaible 3 = Not_required
ThreeDsCardEnrolled	Int	/	0 = Yes 1 = No 2 = unavaible
ExecCode	String (4)	/	The operation result code
ExecMessage	String	/	The operation result description linked to EXECCODE
warrantyresult	String	/	Yes / no
3dsecureversion	Int	/	The kind of 3-D Secure protocol version. Ex : 1
3dsecuremode	Int	/	Applied authentification mode: 0 = ask for a strong authentication 1 = ask for a frictionless authentication
bankauthresult	Int	/	Return code of the authorisation request returned by the issuing bank

Récupérer une Carte Enregistrée

Thibault Bargat — 2020-03-09T11:19:23Z

Pour récupérer les informations relatives à l'enregistrement de la carte de l'utilisateur, veuillez vous référer à l'exemple en marge de droite de cette page.

Les informations sur les différents paramètres de la réponse sont disponible dans le chapitre Ressources.

Requête
GET api/domainePartenaire/cards/registrations/appcardid HTTP/1.1
Accept : application/vnd.s-money.v3+json
Authorization : Bearer ACCESS_TOKEN

Réponse
HTTP/1.1 200 OK
Location : /api/domainePartenaire/cards/registrations/card123

"Card" :
"Id":1380,
"AppCardId" :"card123",
"Network":1,
"Hint" :"423460XXXXXX0001",
"Name" :"carte bancaire enregistrée de user-abc",
"Country" :"FR",
"ExpiryDate" :"2022-12-31T23:59:59"
,
"Status":1,
"UrlReturn" :"http://s-money.fr/urlReturn",
"UrlCallback":null,
"AvailableCards" :"CB",
"ErrorCode":0, "ExtraResults" :
"ThreeDSecure":true,
"ThreeDSecureAuthStatus":0,
"ThreeDSecureSignatureStatus":0,
"ThreeDSecureGlobalStatus":0,
"ThreeDsCardEnrolled":0,
"ExecCode" :"0000",
"ExecMessage" :"Operation succeeded.",
"BankAuthResult":0,
"WarrantyResult":true
,
"Href":null,
"ExtraParameters":null

Si les données détaillées de la carte sont à la valeur "null", c'est qu'elles n'ont pas encore été mises à jour côté Dalenys. Il est nécessaire de relancer l'appel pour avoir la mise à jour de ces données.

Enregistrer une carte bancaire

Thibault Bargat — 2020-03-03T13:00:11Z

2.1 Envoi des données de la requête d'enregistrement carte au serveur S-money

Pour ajouter une carte bancaire, les paramètres obligatoires sont les suivants :
card
appcardid
urlReturn

Les autres paramètres sont optionnels.

Veuillez vous référer à l'exemple présent en marge de droite de cette page, pour l'enregistrement d'une carte bancaire d'un utilisateur.

Le paramètre "href" contient l'url vers laquelle l'application tierce doit rediriger le navigateur client pour effectuer l'enregistrement de la carte.

2.2 Envoie des données de l'enregistrement carte au serveur tiers

Le serveur tiers doit mettre à disposition une url serveur permettant au serveur S-money de le notifier du résultat de l'exécution du paiement.

L'appel du serveur S-money est effectué en méthode HTTP POST.

Les paramètres de la requête HTTP sont :

Paramètre	Type	Description
id	Long	Id de la carte
error	Int	Code d'erreur pour les renseignements carte échoués, 0 si aucune erreur. 1 = Le commerçant doit contacter la banque du porteur 2 = Paiement refusé 3 = Paiement annulé par le client 4 = Porteur non enrôlé 3D-Secure 5 = Erreur authentification 3D-Secure 6 = Erreur technique SystemPay
type	Int	Type de l'opération 5 =enregistrement carte
userid	String	Identifiant de l'utilisateur chez l'application tierce

2.3 Redirection en fin d'enregistrement carte

Le serveur tiers doit mettre à disposition une url permettant au serveur S-money de rediriger le client vers l'environnement tiers.

L'url peut-être soit associée au scheme web (http/https) ou à un scheme privatif dans le cas où l'appel serait effectué à partir d'une application mobile tierce.

L'appel du serveur S-money est effectué en méthode HTTP POST.
Les paramètres de la requête HTTP sont :

Paramètre	Type	Description
Id	Long	Id de la carte bancaire
Type	Int	Type de l'opération 5 = enregistrement carte
Result	Int	Statut de la transaction 0 = Erreur 1 = OK

Requête
POST api/domainePartenaire/users/appuserid/cards/registrations
HTTP/1.1
Accept : application/vnd.s-money.v3+json
Content-Type : application/vnd.s-money.v3+json
Authorization : Bearer ACCESS_TOKEN

{ 
 "card":{ 
 "appcardid":"card123", 
 "name":"ma carte bancaire" 
 }, 
 "Authorizationamount":"0", 
 "urlReturn":"http://url-de-retour-client", 
 "urlCallback":"https://url-de-callback-client", 
 "availableCards":"CB", 
 "holder":{ 
 "name":"holdername", 
 "mail":"holder@mail.fr" 
 } 

}

Réponse
HTTP/1.1 201 CREATED
Location : /api/domainePartenaire/cards/registrations/card123

{ 
 "ExtraData":"{\"IsSchedule\":false,\"IsCardRegistration\":false,\"Profile\":\" hostedfields\",\"UrlReturn\":\"http%253A%252F%252Fwww.google.fr\",\"Cards\":null,\ "FormIntegrationMode\":0}", 
 "Card":{ 
 "Id":517, 
 "AppCardId":"card123", 
 "Network":null, 
 "Hint":null, 
 "Name":"ma carte bancaire", 
 "Country":null, 
 "ExpiryDate":null 
 }, 
 "Status":0, 
 "UrlReturn":null, 
 "UrlCallback":null, 
 "AvailableCards":"CB", 
 "ErrorCode":0, 
 "ExtraResults":null, 
 "Holder":{ 
 "Name":"Pierre Dupont", 
 "Mail":"pierre@dupont.fr" 
 } 

}

Implémentation du formulaire enregistrement

Thibault Bargat — 2020-03-03T13:00:09Z

Principe :

Vous affichez une page d'enregistrement carte comprenant un formulaire de paiement, sauf que les champs de saisie de carte bancaire sont remplacés par des conteneurs de champs hébergés. Ces conteneurs peuvent être n'importe quelle balise HTML : DIV, P, SPAN… la bibliothèque JavaScript des champs hébergés injecte des iframes hébergés par Dalenys dans ces conteneurs, chacun contenant les champs de saisie de données de la carte.

Lors du processus de soumission, vous devrez appeler la méthode Javascript createToken de la bibliothèque de champs hébergés qui déclenchera la création de jetons des données du titulaire de la carte (numéro de carte, date d'expiration et cryptogramme). Si la création de jetons aboutit, vous devez ajouter le jeton reçu à votre demande de soumission de formulaire dans un champ .

Création du formulaire :

Vous devez posséder un certificat TLS (voir en fin de documentation) pour héberger une page de paiement HTTPS valide, sinon le navigateur de l'utilisateur affichera des alertes de sécurité et le bloquera probablement.
La bibliothèque de champs hébergés doit toujours être appelée en ligne. L'utilisation d'une version téléchargée hébergée sur votre propre serveur peut entraîner de graves dysfonctionnements, notamment dans le cas d'une mise à jour de l'API Dalenys.

1- Inclure les librairies javascript suivantes entre les balises …

•

Les identifiants utilisés dans le script pour désigner les champs sont ceux utilisés pour les identifiants des conteneurs créés dans le formulaire. Ceci permettant au script d'injecter les champs hébergés par Dalenys dans ces conteneurs.

5- Charger la bibliothèque des champs hébergés

À ce stade, votre navigateur Web peut afficher les champs de saisie de la carte bancaire dans leurs conteneurs.

6- Générer le jeton

A la soumission du formulaire, vous devez appeler la méthode CREATETOKEN() sur l'événement ONSUBMIT() pour déclencher le processus de création de jetons.

Cette méthode attend un paramètre de rappel qui sera déclenché une fois la demande de tokénisation terminée.

Votre rappel recevra un objet de résultat contenant ces propriétés :

execCode : code de résultat technique de l'appel tokenization. En cas de succès, 0000 sera envoyé
message : la description liée à l'execCode
cardType : le type de carte
cardCode : Les 6 premiers et les 4 derniers chiffres du numéro de la carte du titulaire
cardValidityDate : Date d'expiration de la carte
hfToken : le jeton généré

En cas de succès, vous devez ajouter le jeton reçu à la demande d'envoi de formulaire dans une balise

7- Inclure la propriété Smoney EXTRADATA (issues du résultat de l'appel api pour enregistrer la carte bancaire) en champs hidden en plus de celui du jeton.

Les attributs « name » des balises input hidden ne doivent pas être changés.

Enregistrement carte avec authentification 3DSecure :

Selon la carte enregistrée et son enrollement 3DSecure, une authentification 3DSecure peut être nécessaire.

Dans ce cas, en réponse à l'action du formulaire, la page HTML du formulaire 3DSecure est envoyée en contenu de la réponse accompagnée d'un http status code 200 (OK). La soumission du formulaire 3DSecure se terminera par une redirection 302 vers l'url renseignée dans le champ urlReturn de la requête initiale.

Dans le cas contraire, une réponse 302 (redirect) est directement faite et redirige le navigateur de l'utilisateur vers l'url renseignée dans le champ urlReturn de la requête initiale.

Ressources

Thibault Bargat — 2020-03-03T12:56:42Z