Contenu :
Introduction
When purchasing online, a consumer may be confronted with the security protocol 3-D Secure to verify that he is the holder of the means of payment used. This procedure involves the entry on an authentication form of a code transmitted by SMS. The merchant's brand name is then displayed in the SMS and on the authentication page displayed to the consumer.
You can customize the sign name, either in the configuration of the average payment contract or during each transaction in the payment API call.
How to customize the name of the merchant?
With Payline's Payline Center Payment Method
When setting up the Payment Method contract in the Administration Center, the activation of the "3Dsecure" option allows you to enter the name of the merchant that will be used:
With the Payline API
By populating the MERCHANTNAME tag with one of the doWebPayment, manageWebWallet, and verifyEnrollment services.
- service doWebPayment.merchantName
- service manageWebWallet.merchantName
- service doAuthorization puis service verifyEnrollement.merchantName
Le champ is an alphanumeric (25) accepting the following special characters: & is '' (- è_çà) = ^ $ ù *,;:! ~ # {[| `\ ^ @}} ¨ £% μ? ./§ < > ° +
Example of displaying the sign name in the 3D Secure authentication page
The ACS authentication page
Recall of the sign name used in the administration center
The brand name will be displayed in the "3DSecure and Payment Guarantee" insert of the transaction details:
Code Examples for the WebService API
Service doWebPayment
< doWebPaymentRequest > < version >…</ version > < payment >…</ payment > < returnURL >…</ returnURL > < cancelURL >…</ cancelURL > < order >…</ order > < notificationURL >…</ notificationURL > < selectedContractList >…</ selectedContractList > < secondSelectedContractList >…</ secondSelectedContractList > < privateDataList >…</ privateDataList > < languageCode >…</ languageCode > < customPaymentPageCode >…</ customPaymentPageCode > < buyer >…</ buyer > < owner >…</ owner > < securityMode >…</ securityMode > < recurring >…</ recurring > < customPaymentTemplateURL >…</ customPaymentTemplateURL > < contractNumberWalletList >…</ contractNumberWalletList > < merchantName >Votre nom d'enseigne</ merchantName > </ doWebPaymentRequest > |
Service manageWebWallet
< manageWebWalletRequest > < version >…</ version > < contractNumber >…</ contractNumber > < selectedContractList >…</ selectedContractList > < updatePersonalDetails >…</ updatePersonalDetails > < updateOwnerDetails >…</ updateOwnerDetails > < updatePaymentDetails >…</ updatePaymentDetails > < buyer >…</ buyer > < owner >…</ owner > < languageCode >…</ languageCode > < customPaymentPageCode >…</ customPaymentPageCode > < securityMode >…</ securityMode > < returnURL >…</ returnURL > < cancelURL >…</ cancelURL > < notificationURL >…</ notificationURL > < privateDataList >…</ privateDataList > < customPaymentTemplateURL >…</ customPaymentTemplateURL > < contractNumberWalletList >…</ contractNumberWalletList > < merchantName >Votre nom d'enseigne</ merchantName > </ manageWebWalletRequest > |
Service verifyEnrollment
< verifyEnrollmentRequest > < version >…</ version > < card >…</ card > < payment >…</ payment > < orderRef >…</ orderRef > < mdFieldValue >…</ mdFieldValue > < userAgent >…</ userAgent > < walletId >…</ walletId > < walletCardInd >…</ walletCardInd > < generateVirtualCvx >…</ generateVirtualCvx > < merchantName >Votre nom d'enseigne</ merchantName > </ verifyEnrollmentRequest > |
Reporting
You can also retrieve the used sign name by selecting the MERCHANTNAME_3D_SECURE field in the export template.
Contenu :
Introduction
When purchasing online, a consumer may be confronted with the security protocol 3-D Secure to verify that he is the holder of the means of payment used. This procedure involves the entry on an authentication form of a code transmitted by SMS. The merchant's brand name is then displayed in the SMS and on the authentication page displayed to the consumer.
You can customize the sign name, either in the configuration of the average payment contract or during each transaction in the payment API call.
How to customize the name of the merchant?
With Payline's Payline Center Payment Method
When setting up the Payment Method contract in the Administration Center, the activation of the "3Dsecure" option allows you to enter the name of the merchant that will be used:
With the Payline API
By populating the MERCHANTNAME tag with one of the doWebPayment, manageWebWallet, and verifyEnrollment services.
- service doWebPayment.merchantName
- service manageWebWallet.merchantName
- service doAuthorization puis service verifyEnrollement.merchantName
Le champ is an alphanumeric (25) accepting the following special characters: & is '' (- è_çà) = ^ $ ù *,;:! ~ # {[| `\ ^ @}} ¨ £% μ? ./§ < > ° +
Example of displaying the sign name in the 3D Secure authentication page
The ACS authentication page
Recall of the sign name used in the administration center
The brand name will be displayed in the "3DSecure and Payment Guarantee" insert of the transaction details:
Code Examples for the WebService API
Service doWebPayment
< doWebPaymentRequest > < version >…</ version > < payment >…</ payment > < returnURL >…</ returnURL > < cancelURL >…</ cancelURL > < order >…</ order > < notificationURL >…</ notificationURL > < selectedContractList >…</ selectedContractList > < secondSelectedContractList >…</ secondSelectedContractList > < privateDataList >…</ privateDataList > < languageCode >…</ languageCode > < customPaymentPageCode >…</ customPaymentPageCode > < buyer >…</ buyer > < owner >…</ owner > < securityMode >…</ securityMode > < recurring >…</ recurring > < customPaymentTemplateURL >…</ customPaymentTemplateURL > < contractNumberWalletList >…</ contractNumberWalletList > < merchantName >Votre nom d'enseigne</ merchantName > </ doWebPaymentRequest > |
Service manageWebWallet
< manageWebWalletRequest > < version >…</ version > < contractNumber >…</ contractNumber > < selectedContractList >…</ selectedContractList > < updatePersonalDetails >…</ updatePersonalDetails > < updateOwnerDetails >…</ updateOwnerDetails > < updatePaymentDetails >…</ updatePaymentDetails > < buyer >…</ buyer > < owner >…</ owner > < languageCode >…</ languageCode > < customPaymentPageCode >…</ customPaymentPageCode > < securityMode >…</ securityMode > < returnURL >…</ returnURL > < cancelURL >…</ cancelURL > < notificationURL >…</ notificationURL > < privateDataList >…</ privateDataList > < customPaymentTemplateURL >…</ customPaymentTemplateURL > < contractNumberWalletList >…</ contractNumberWalletList > < merchantName >Votre nom d'enseigne</ merchantName > </ manageWebWalletRequest > |
Service verifyEnrollment
< verifyEnrollmentRequest > < version >…</ version > < card >…</ card > < payment >…</ payment > < orderRef >…</ orderRef > < mdFieldValue >…</ mdFieldValue > < userAgent >…</ userAgent > < walletId >…</ walletId > < walletCardInd >…</ walletCardInd > < generateVirtualCvx >…</ generateVirtualCvx > < merchantName >Votre nom d'enseigne</ merchantName > </ verifyEnrollmentRequest > |
Reporting
You can also retrieve the used sign name by selecting the MERCHANTNAME_3D_SECURE field in the export template.