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
Copy file name to clipboardExpand all lines: docs/API-Extension-Setup.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,7 @@ Variables that begin with 'CT' prefix are Commercetools project specific propert
22
22
| PAYMENT_GATEWAY_MERCHANT_ID | Your Cybersource merchant Id | Provided by Cybersource |
23
23
| PAYMENT_GATEWAY_MERCHANT_KEY_ID | Id of a Cybersource shared secret key to be used for HTTP Signature authentication | Created in [key-Creation\#Cybersource](Key-Creation.md#Cybersource). |
24
24
| PAYMENT_GATEWAY_MERCHANT_SECRET_KEY | Value of a Cybersource shared secret key to be used for HTTP Signature authentication | Created in [key-Creation\#Cybersource](key-Creation.md#Cybersource). |
25
+
| PAYMENT_GATEWAY_SHIPPING_METHOD | Shipping method to be passed in shipTo.method field | The value should be any of the following: lowcost, sameday, oneday, twoday, threeday, pickup, other or none. |
25
26
| PAYMENT_GATEWAY_TARGET_ORIGINS | Base URLs where your frontend will be accessible | Used for Card payment method. Comma separated value without any spaces |
26
27
| PAYMENT_GATEWAY_VERIFICATION_KEY | Used to check Flex tokens for tampering | Use <b>Openssl -rand64 32 </b>command to generate verification key |
27
28
| PAYMENT_GATEWAY_CC_ALLOWED_CARD_NETWORKS | csv(comma separated value) of the card networks | If not specified extension will support all the card networks(VISA, MASTERCARD, AMEX, DISCOVER, MAESTRO, CUP, JCB, CARTESBANCAIRES & DINERSCLUB) by default. Case sensitive. Accepts block letters only without any spaces – eg: VISA,AMEX |
| 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.
Copy file name to clipboardExpand all lines: docs/Process-a-Card-Payment-With-Payer-Authentication.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,6 +30,7 @@ After authentication is complete, authorization of the payment can then be tri
30
30
| region | shipTo_state | billTo_state ||
31
31
| country | shipTo_country | billTo_country ||
32
32
| email | shipTo_email | billTo_email ||
33
+
| phone | shipTo_phone | billTo_phone ||
33
34
34
35
2. Tokenize Card details using Cybersource Flex
35
36
@@ -75,7 +76,7 @@ After authentication is complete, authorization of the payment can then be tri
75
76
76
77
a. Also see [Decision Manager](Decision-Manager.md) for additional fields to populate if you are using Decision Manager
77
78
78
-
b. When the payment is being updated, the extension will do a Payer Setup call to get reference_id for Digital Wallets to use in place of BIN number in Cardinal.
79
+
b. When the payment is being updated, the extension will do a Payer Auth Setup call to get reference_id for Digital Wallets to use in place of BIN number in Cardinal.
79
80
80
81
Skip this step for saved token and proceed to step c
81
82
@@ -91,7 +92,7 @@ After authentication is complete, authorization of the payment can then be tri
91
92
| custom.fields.isv_saleEnabled | false | Yes | Set the value to true if sale is enabled |
92
93
93
94
94
-
c. For saved token, when the payment is being updated, the extension will do a Payer Setup call to get reference_id for Digital Wallets to use in place of BIN number in Cardinal.
95
+
c. For saved token, when the payment is being updated, the extension will do a Payer Auth Setup call to get reference_id for Digital Wallets to use in place of BIN number in Cardinal.
@@ -115,6 +116,9 @@ After authentication is complete, authorization of the payment can then be tri
115
116
| custom.fields.isv_acceptHeader | Accept header from Customer browser | Yes | Used by 3DS process, populated from client-side libraries |
116
117
| custom.fields.isv_userAgentHeader | User agent header from Customer browser | Yes | Used by 3DS process, populated from client-side libraries |
117
118
| custom.fields.isv_customerIpAddress | Customer IP address | Yes | Populated from client-side libraries |
119
+
| custom.fields.isv_screenWidth | Screen width of Customer browser | Yes | Used by 3DS process, populated from client-side libraries |
120
+
| custom.fields.isv_screenHeight | Screen height of Customer browser | Yes | Used by 3DS process, populated from client-side libraries |
121
+
118
122
119
123
8. wait for the response from ddc form and if successful, then proceed with enrolment, verify the following fields from update response
120
124
@@ -124,7 +128,7 @@ After authentication is complete, authorization of the payment can then be tri
124
128
isv_payerEnrollHttpCode
125
129
isv_payerEnrollStatus
126
130
127
-
9. Check if the `isv_payerEnrollHttpCode` value is 201 and `isv_payerEnrollStatus` value "CUSTOMER_AUTHENTICATION_REQUIRED" from the updated response. If yes, repeat the steps from 6 else proceed to step 10
131
+
9. Check if the `isv_payerEnrollHttpCode` value is 201 and `isv_payerEnrollStatus` value "CUSTOMER_AUTHENTICATION_REQUIRED" from the updated response. If yes, repeat the steps from 5 else proceed to step 10. Refer the [DMPA](./Decision-Manager.md#payer-authentication-with-decision-manager) section to know more about the DMPA
128
132
129
133
10. Check the value of the isv_payerAuthenticationRequired field on the
130
134
updated payment. If the value is true, perform the following steps
@@ -146,7 +150,7 @@ After authentication is complete, authorization of the payment can then be tri
146
150
isv_payerEnrollHttpCode
147
151
isv_payerEnrollStatus
148
152
149
-
Check if the isv_payerEnrollHttpCode value is 201 and isv_payerEnrollStatus value "CUSTOMER_AUTHENTICATION_REQUIRED" from the updated response. If yes, repeat the steps from 6 else proceed to step 12.
153
+
Check if the isv_payerEnrollHttpCode value is 201 and isv_payerEnrollStatus value "CUSTOMER_AUTHENTICATION_REQUIRED" from the updated response. If yes, repeat the steps from 5 else proceed to step 12.
0 commit comments