Using the embedded form
Affected use cases
- Immediate payment with card detail entry
- Payment by token
- Suggestion to register the card upon payment
- Card registration upon payment
- Card registration in buyer’s wallet (with or without payment)
Payment process
Initialization of the payment session
This use case requires the creation of aformTokenvia a call to theCharge/CreatePaymentWeb Service.
No specific fields are necessary in order to benefit from the 3D Secure protection.
Use the fields below to build your request:
| NAME | DESCRIPTION | REQUIRED |
|---|---|---|
| amount | Amount for which authentication is requested. | Yes |
| currency | Alphanumeric code of the currency. | Yes |
| orderId | Order reference. This field is recommended. | No |
| formAction | Type of desired behavior when a transaction is being created. | No |
| customer | Object containing buyer’s data. | No |
Depending on the use case (i.e. the value of the fieldformAction), strong authentication may be required. In this case, thestrongAuthenticationfield is ignored.
| Use case | formAction | Strong authentication required? |
|---|---|---|
| Single payment | PAYMENT | The authentication type depends on the issuer’s decision. For payments in euro, the merchant can request an exemption from strong authentication if the amount is less than €30 and if the shop has the “Frictionless 3DS2” option. For payments made in another currency, the merchant can request authentication without interaction with the cardholder if the shop has the “Frictionless 3DS2” option. |
| Payment by token | PAYMENT | Strong authentication and CVV entry required. |
| Card registration upon payment | REGISTER_PAY | Strong authentication required. |
| Suggestion to register the card upon payment | ASK_REGISTER_PAY | Strong authentication required only if the buyer accepts to register their payment method. Otherwise, the behavior is identical to thePAYMENTvalue. |
| Payment using the buyer’s wallet | CUSTOMERWALLET | Strong authentication required only if the buyer accepts to register their payment method or if they are using an already registered card. In all other cases, the behavior is identical to thePAYMENTvalue. |
Response analysis
At the end of the operation, the gateway returns an objectPaymentto the notification URL of the merchant site and to the JavaScript client.
Here is a list of attributes describing the cardholder authentication result according to the use case:
| Use case | Returned fields |
|---|---|
| Transaction with successful strong authentication |
|
| Transaction with frictionless authentication successfully completed, the merchant has the “Frictionless 3DS2” option and has requested authentication without cardholder interaction. |
|
| Transaction with frictionless authentication successfully completed, the merchant has not requested authentication without cardholder interaction. |
|
| Transaction with failed 3D Secure authentication |
|
| Card not enrolled. |
|