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
| isv_authorizationStatus | String | false |This field will be updated with the initial authorization or sale status from the payment gateway. If Cybersource response doesn't reach the extension, this field will remain empty|
Copy file name to clipboardExpand all lines: docs/Decision-Manager.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,23 @@ The Cybersource Extension has environment variable for decision manager as `PAYM
40
40
41
41
> **_NOTE:_** Value for `PAYMENT_GATEWAY_DECISION_SYNC_MULTI_MID` is case sensitive without any spaces.
42
42
43
+
### Payer Authentication with Decision Manager
44
+
45
+
You can use Decision Manager with payer authentication services to allow the risk of an order to determine when you need to invoke payer authentication.
46
+
Merchant can choose to set the following rules in Decision Manager profile
47
+
48
+
1.`PAYERAUTH_INVOKE` profile.
49
+
50
+

51
+
2.`PAYERAUTH_EXTERNAL` profile.
52
+
53
+

54
+
3.`PAYERAUTH_SKIP` profile.
55
+
56
+

57
+
58
+
To see more about Payer Authentication with decision manager, refer [this](https://ebc.cybersource.com/content/ebc/docs/cybs/en-us/html/dm-develop/developer/all/so/oxy_ex-1/topics/c_Using_DM_With_Payer_Auth.html)
59
+
43
60
## Optional fields
44
61
45
62
To pass additional data to Decision Manager, it is possible to customize the Commercetools resources to add extra fields. If these fields exist and there are values present for these, then the extension will pass the values on to Cybersource in the appropriate request
Copy file name to clipboardExpand all lines: docs/Docker-Container-in-Azure.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ Replace value of the following
124
124
125
125
Once `deploy-aci.yaml` is ready with all the values, navigate to the directory where file is present and run the following command
126
126
127
-
az container create --resource-group rg-visa-qa --file deploy-aci.yaml
127
+
az container create --resource-group <name of resource group> --file deploy-aci.yaml
128
128
129
129
**_NOTE:_** In `deploy-aci.yaml` file, make sure to mention all the existing variables since modification with yaml file will override all the existing variables.
130
130
@@ -146,4 +146,4 @@ Once `deploy-aci.yaml` is ready with all the values, navigate to the directory w
146
146
147
147
3. While modifying container instance, if you are getting "internal server error", it means value provided in deploy-aci.yaml is incorrect, make sure to provide correct values for all the fields.
148
148
149
-
4. If you are getting "Gateway Timeout" after hitting container's FQDN, it might be possible that incorrect value is being passed for DNS name label scope reuse field or value for CONFIG_PORT environment variable is not provided. If PAYMENT_GATEWAY_SERVERLESS_DEPLOYMENT environment variable is set to 'azure', then providing value for FUNCTIONS_HTTPWORKER_PORT is must.
149
+
4. If you are getting "Gateway Timeout" after hitting container's FQDN, it might be possible that incorrect value is being passed for DNS name label scope reuse field or value for CONFIG_PORT environment variable is not provided. If PAYMENT_GATEWAY_SERVERLESS_DEPLOYMENT environment variable is set to 'azure', then providing value for FUNCTIONS_HTTPWORKER_PORT is must.
0 commit comments