Skip to content

Commit d0d0ba5

Browse files
jbransvisajbransvisa
authored
Merge pull request #26 from jbransvisa/master
v24.3.1
2 parents 3033719 + ac199b0 commit d0d0ba5

File tree

107 files changed

+7334
-5717
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

107 files changed

+7334
-5717
lines changed

‎.env‎

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,9 @@ PAYMENT_GATEWAY_EXTENSION_HEADER_VALUE =
55
PAYMENT_GATEWAY_RUN_ENVIRONMENT =
66
PAYMENT_GATEWAY_ENABLE_DEBUG =
77

8-
PAYMENT_GATEWAY_MERCHANT_ID =
9-
PAYMENT_GATEWAY_MERCHANT_KEY_ID =
10-
PAYMENT_GATEWAY_MERCHANT_SECRET_KEY =
11-
8+
PAYMENT_GATEWAY_MERCHANT_ID =
9+
PAYMENT_GATEWAY_MERCHANT_KEY_ID =
10+
PAYMENT_GATEWAY_MERCHANT_SECRET_KEY =
1211

1312
PAYMENT_GATEWAY_TARGET_ORIGINS =
1413
PAYMENT_GATEWAY_VERIFICATION_KEY =
@@ -31,8 +30,7 @@ PAYMENT_GATEWAY_DECISION_SYNC =
3130
PAYMENT_GATEWAY_DECISION_MANAGER =
3231
PAYMENT_GATEWAY_RUN_SYNC =
3332
PAYMENT_GATEWAY_DECISION_SYNC_MULTI_MID =
34-
PAYMENT_GATEWAY_NETWORK_TOKEN_MULTI_MID =
35-
33+
PAYMENT_GATEWAY_NETWORK_TOKEN_MULTI_MID =
3634

3735
PAYMENT_GATEWAY_UC_ALLOWED_PAYMENTS =
3836
PAYMENT_GATEWAY_UC_BILLING_TYPE =
@@ -49,4 +47,4 @@ CT_PROJECT_KEY =
4947
CT_CLIENT_ID =
5048
CT_CLIENT_SECRET =
5149
CT_AUTH_HOST =
52-
CT_API_HOST =
50+
CT_API_HOST =

‎docs/Commercetools-Setup.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -160,6 +160,7 @@ Fields
160160
| isv_responseCode | String | false ||
161161
| isv_dmpaFlag | Boolean | false ||
162162
| isv_shippingMethod | String | false ||
163+
| isv_metadata | String | false ||
163164

164165
### Payer Authentication enrolment check
165166

‎docs/Process-a-Card-Payment-With-Payer-Authentication.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,6 +91,7 @@ After authentication is complete, authorization of the payment can then be tri
9191
| custom.fields.isv_deviceFingerprintId | Customer device fingerprint Id | Yes | Refer [Device Fingerprinting](./Decision-Manager.md#device-fingerprinting) to generate this value |
9292
| custom.fields.isv_saleEnabled | false | Yes | Set the value to true if sale is enabled |
9393
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
94+
| custom.fields.isv_metadata | Metadata for the order | No | This field can be used to send additional custom data as part of the authorization request. The data should be serialized into a string format (e.g., JSON string) before passing it in the request.<br>**Example:**"isv_metadata": "{\"1\":\"value1\", \"2\":\"value2\"}" |
9495

9596

9697
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.
@@ -102,7 +103,8 @@ After authentication is complete, authorization of the payment can then be tri
102103
| custom.fields.isv_cardExpiryMonth | Card expiry month | No | custom.fields.isv_tokens's "cardExpiryMonth" value from Customer object <br>Not required by the extension but used for display |
103104
| custom.fields.isv_cardExpiryYear | Card expiry year | No | custom.fields.isv_tokens's "cardExpiryYear" value from Customer object <br>Not required by the extension but used for display |
104105
| custom.fields.isv_deviceFingerprintId | Customer device fingerprint Id | Yes | Refer [Device Fingerprinting](./Decision-Manager.md#device-fingerprinting) to generate this value |
105-
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
106+
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
107+
| custom.fields.isv_metadata | Metadata for the order | No | This field can be used to send additional custom data as part of the authorization request. The data should be serialized into a string format (e.g., JSON string) before passing it in the request.<br>**Example:**"isv_metadata": "{\"1\":\"value1\", \"2\":\"value2\"}" |
106108

107109

108110
6. Wait for the event to return back the following fields, verify them from update response. If the data exists for below fields, submit the device data collection form using below data, else throw error to the user. See [Device Data Collection](https://developer.cybersource.com/docs/cybs/en-us/payer-authentication/developer/all/rest/payer-auth/pa2-ccdc-ddc-intro.html) to get more details about device data collection Iframe

‎docs/Process-a-Card-Payment-Without-Payer-Authentication.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,9 @@ Processing of a payment is triggered by adding an initial transaction to a Comme
8989
| custom.fields.isv_deviceFingerprintId | Customer device fingerprint Id | Yes | Should pass this field to extension, if Decision Manager is enabled.Refer [Device Fingerprinting](./Decision-Manager.md#device-fingerprinting) to generate this value |
9090
| custom.fields.isv_customerIpAddress | Customer IP address | No | Populated from client-side libraries |
9191
| custom.fields.isv_saleEnabled | false | Yes | Set the value to true if sale is enabled |
92-
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
92+
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
93+
| custom.fields.isv_metadata | Metadata for the order | No | This field can be used to send additional custom data as part of the authorization request. The data should be serialized into a string format (e.g., JSON string) before passing it in the request.<br>**Example:**"isv_metadata": "{\"1\":\"value1\", \"2\":\"value2\"}" |
94+
9395

9496
6. Add a transaction to the payment with the following values populated
9597

‎docs/Process-a-Payment-ApplePay.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,9 @@
5858
| custom.fields.isv_customerIpAddress | Customer IP address | Yes | Populated from client-side libraries |
5959
| custom.fields.isv_saleEnabled | false | Yes | Set the value to true if sale is enabled |
6060
| custom.fields.isv_walletType | Wallet type | No | This value is required if walletType is to be passed in authorization. Refer [Cybersource Processing a Payment](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments_process-a-payment) for more information about the wallet type value to be passed. It is supported only for ApplePay, ClicktoPay and GooglePay payment methods|
61-
|custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
61+
|custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
62+
| custom.fields.isv_metadata | Metadata for the order | No | This field can be used to send additional custom data as part of the authorization request. The data should be serialized into a string format (e.g., JSON string) before passing it in the request.<br>**Example:**"isv_metadata": "{\"1\":\"value1\", \"2\":\"value2\"}" |
63+
6264

6365
4. Add the payment to the cart
6466

‎docs/Process-a-Payment-ClicktoPay.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,9 @@ The shipping address should be acquired from Visa Click to Pay. This can be set
4848
| custom.fields.isv_saleEnabled | false | Yes | Set the value to true if sale is enabled |
4949
| custom.fields.isv_walletType | Wallet type | No | This value is required if walletType is to be passed in authorization. Refer [Cybersource Processing a Payment](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments_process-a-payment) for more information about the wallet type value to be passed. It is supported only for ApplePay, ClicktoPay and GooglePay payment methods|
5050
| custom.fields.isv_merchantId | Merchant Id used for the transaction | No | Required when you want to support Multi-Mid functionality. Populate this field with the value of merchant Id in which the transaction should happen. When this field is empty, default mid configuration will be considered for the transaction. The same mid will be used for the follow-on transactions. |
51-
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
51+
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
52+
| custom.fields.isv_metadata | Metadata for the order | No | This field can be used to send additional custom data as part of the authorization request. The data should be serialized into a string format (e.g., JSON string) before passing it in the request.<br>**Example:**"isv_metadata": "{\"1\":\"value1\", \"2\":\"value2\"}" |
53+
5254

5355
3. Add the payment to the cart
5456

‎docs/Process-a-Payment-GooglePay.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,8 +30,9 @@
3030
| custom.fields.isv_saleEnabled | false | Yes | Set the value to true if sale is enabled |
3131
| custom.fields.isv_walletType | Wallet type | No | This value is required if walletType is to be passed in authorization. Refer [Cybersource Processing a Payment](https://developer.cybersource.com/api-reference-assets/index.html#payments_payments_process-a-payment) for more information about the wallet type value to be passed. It is supported only for ApplePay, ClicktoPay and GooglePay payment methods|
3232
| custom.fields.isv_merchantId | Merchant Id used for the transaction | No | Required when you want to support Multi-Mid functionality. Populate this field with the value of merchant Id in which the transaction should happen. When this field is empty, default mid configuration will be considered for the transaction. The same mid will be used for the follow-on transactions. |
33-
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
34-
33+
| custom.fields.isv_shippingMethod | Shipping method for the order | No | Possible values: <ul> <li> `lowcost`: Lowest-cost service </li> <li>`sameday`: Courier or same-day service </li> <li>`oneday`: Next-day or overnight service </li> <li>`twoday`: Two-day service </li> <li>`threeday`: Three-day service.</li> <li> `pickup`: Store pick-up </li> <li> `other`: Other shipping method </li> <li> `none`: No shipping method because product is a service or subscription </li> |
34+
| custom.fields.isv_metadata | Metadata for the order | No | This field can be used to send additional custom data as part of the authorization request. The data should be serialized into a string format (e.g., JSON string) before passing it in the request.<br>**Example:**"isv_metadata": "{\"1\":\"value1\", \"2\":\"value2\"}" |
35+
3536
3. Add the payment to the cart
3637

3738
4. Add a transaction to the payment

0 commit comments

Comments
 (0)