You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- SSE Development Best Practices ( [HTML](https://community.oracle.com/groups/oracle-commerce-cloud-group/blog/2018/11/08/server-side-extension-development-best-practices) )
70
-
- Developing Widgets in OCC ( [HTML](https://docs.oracle.com/en/cloud/saas/cx-commerce/20c/widge/create-widget1.html) )
67
+
- SSE Development Best Practices ( [HTML](https://community.oracle.com/customerconnect/discussion/630679/server-side-extension-development-best-practices) )
68
+
- Developing OSF in OCC ( [HTML](https://docs.oracle.com/en/cloud/saas/cx-commerce/dosfa/index.html) )
71
69
- Cybersource REST API Reference ( [HTML](https://developer.cybersource.com/api-reference-assets/index.html) )
|**paymentMethodTypes**| Enabled Payment Methods. 'Credit & Debit Card' should be enabled |
44
45
|**paymentOptions**| Payment options enabled for payment using Payment Widget. 'Credit & Debit Card' should be enabled |
45
-
|**payerAuthEnabled**| Enables payer authentication (3D Secure) for credit cards |||
46
+
|**payerAuthEnabled**| Enables payer authentication (3D Secure) for credit cards |
47
+
|**scaEnabled**| If enabled card holder will be 3DS Challenged when saving a card |
46
48
|**saleEnabled**| Indicates if authorizing and taking payment will be done at the same time |
47
49
|**isCVVRequiredForSavedCards**| Should be disabled as CVV is not required in backend |
48
50
|**isCVVRequiredForScheduledOrders**| Should be disabled as CVV is not required in backend |
49
51
50
52
Default values:
51
53
52
54
-`payerAuthEnabled`: true. Payer authentication is enabled by default
55
+
-`scaEnabled` : false
53
56
-`isCVVRequiredForSavedCards`: false
54
57
-`isCVVRequiredForScheduledOrders`: false
55
58
-`saleEnabled` - by default SALE is disabled for Card payments. Can be enabled in OCC Admin
@@ -135,7 +138,6 @@ plugins
135
138
| | | ├── meta.js
136
139
| | | └── styles.css
137
140
| | ├── isv-payment-utility
138
-
| | | ├── common.js
139
141
| | | ├── flex-microform.js
140
142
| | | ├── flex-microForm-api.js
141
143
| | | └── script-loader.js
@@ -145,7 +147,9 @@ plugins
145
147
| | ├── meta.js
146
148
| | └── styles.css
147
149
| ├── .eslintrc
150
+
| ├── constants.js
148
151
| ├── index.js
152
+
| ├── isv-common.js
149
153
| └── meta.js
150
154
├── endpoints
151
155
| ├── flex-microform-endpoint
@@ -261,10 +265,20 @@ The following UI component contains Payer Authentication integration logic `plug
261
265
262
266
#### Backend (SSE) integration details
263
267
264
-
-`server-extension/src/controllers/payerAuth.ts` Controller for generating a signed PayerAuth JWT
268
+
-`server-extension/src/controllers/payerAuth.ts` Controller for payer auth setup
265
269
-`server-extension/src/services/payments/converters/request/mappers/payerAuthEnrollMapper.ts` Including payer auth reference id into PSP card authorization request
266
270
-`server-extension/src/services/payments/converters/request/mappers/payerAuthValidationMapper.ts` Including payer auth validation token into PSP card authorization request
267
271
272
+
#### Strong Customer Authentication (SCA)
273
+
274
+
When `Payer Authentication` is enabled, if a transaction gets declined with the reason as Strong Customer Authentication required, then another request will be sent from Oracle Commerce Cloud automatically for the same order and the customer will be 3DS challenged.
275
+
276
+
In case merchants would like the cardholder to be 3DS Challenged when saving a card `scaEnabled` gateway setting can be updated to enable it for credit cards.
277
+
278
+
In case 'Strong Customer Authentication' is enabled for credit cards, '10000' response code is sent back in Webhook response so that OCC becomes aware of that.
279
+
280
+
*Note:* The `scaEnabled` setting is applicable only if `Payer Authentication` is enabled.
281
+
268
282
### Capturing funds during authorization (SALE)
269
283
270
284
In case merchants would like funds to be captured (settled) during card authorizations `saleEnabled` gateway setting can be updated to enable it for credit cards.
0 commit comments