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: documentation/installation.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -44,9 +44,9 @@ You need to build all packages at once using `yarn build:prod` command from proj
44
44
45
45
### Configure gateway
46
46
47
-
Before installing payment gateway you should decide whether you will support all payment methods or only some of it. There are two ways you can manage it:
47
+
Before installing a payment gateway you should decide whether you will support all payment methods or only some. There are two ways it can be managed:
48
48
49
-
1. Disabling payment type from OCC Admin interface which will result in payment option not being rendered in UI (Payment Widget)
49
+
1. Disabling payment type from OCC Admin interface which will result in the payment option not being rendered in UI (Payment Widget)
50
50
2. Removing unrelated configuration properties from `packages/payment-gateway/gateway/isv-occ-gateway/config/config.json`
51
51
52
52
 In most cases just disabling unsupported payment type from OCC Admin is preferable. Removing unsupported configuration properties can be done in case particular payment types (e.g. GooglePay) should be initially excluded from OCC Admin interface.
@@ -91,7 +91,7 @@ After successful deployment you will need to enable payment gateway:
91
91
- Configure gateway settings by providing values (e.g. merchant credentials) for particular channel (Preview, Storefront, Agent)
92
92
- Save Changes
93
93
- Go back to the 'Payment Types' type
94
-
- Select supported credit card types from the list [Possible card types: VISA, MASTERCARD, AMEX, DISCOVER, DINERSCLUB, JCB, CARTESBANCAIRES, MAESTRO, CARNET, CUP]
94
+
- Select supported credit/debit card types from the list [Possible card types: VISA, MASTERCARD, AMEX, DISCOVER, DINERSCLUB, JCB, CARTESBANCAIRES, MAESTRO, CARNET, CUP]
95
95
- You might want to also provide list of supported billing countries as well as default one
Copy file name to clipboardexpand all lines: documentation/occ.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@
11
11
|[Package Contents](package-contents.md)| Detailed explanation of each package included into solution. Documents available payment gateway settings |
12
12
|[Installation](installation.md)| Go through installation steps to deploy and configure payment extensions to OCC |
13
13
|_Payment Services_||
14
-
|[Credit Card](payment-services/credit-card.md)| Detailed information about credit card payment services, e.g. FlexMicroform integration, Payer Authentication (3DSecure) etc |
14
+
|[Credit Card](payment-services/credit-card.md)| Detailed information about credit card payment services, e.g.Microform integration, Payer Authentication (3DSecure) etc |
15
15
|[GooglePay](payment-services/googlepay.md)| Documents GooglePay integration and related technical details |
16
16
|[ApplePay](payment-services/applepay.md)| Documents ApplePay integration and related technical details. Includes ApplePay setup steps |
17
17
|[Settlement and Refund](payment-services/settlement-refund.md)| Additional payment services to allow fulfillment processes to settle or refund particular transactions when needed |
@@ -27,13 +27,13 @@ The Credit Card payment service provides the following operations:
27
27
28
28
The following applies to credit card payments:
29
29
30
-
- Credit card payments using [FlexMicroform v2](https://developer.cybersource.com/api/developer-guides/dita-flex/SAFlexibleToken/FlexMicroform.html). The transient token represents both card number (PAN) and CVV. Only token, card expiration date and masked card number going to be sent in a webhook request.
30
+
- Credit card payments using [Microform v2](https://developer.cybersource.com/api/developer-guides/dita-flex/SAFlexibleToken/FlexMicroform.html). The transient token represents both card number (PAN) and CVV. Only token, card expiration date and masked card number going to be sent in a webhook request.
31
31
- Payer Authentication (3D Secure)
32
32
- Shopper can choose to save credit card as part of profile
33
33
- Subscribe to Network Token life cycle updates
34
34
- Shopper can pay with a saved card
35
35
36
-
 With Flex Microform, the capture of card number and security code (CVV) are fully outsourced to the payment provider, which can qualify merchants for SAQ A-based assessments. Flex Microform provides the most secure method for tokenizing card data. Sensitive data is encrypted on the customer's device before HTTPS transmission to the payment provider. This method mitigates any compromise of the HTTPS connection through a man in the middle attack.
36
+
 With Microform, the capture of card number and security code (CVV) are fully outsourced to the payment provider, which can qualify merchants for SAQ A-based assessments. Microform provides the most secure method for tokenizing card data. Sensitive data is encrypted on the customer's device before HTTPS transmission to the payment provider. This method mitigates any compromise of the HTTPS connection through a man in the middle attack.
37
37
38
38
## Implementation Details
39
39
@@ -61,7 +61,7 @@ Default values:
61
61
-`isCVVRequiredForScheduledOrders`: false
62
62
-`saleEnabled` - by default SALE is disabled for Card payments. Can be enabled in OCC Admin
63
63
64
-
### FlexMicroform Card Payments
64
+
### Microform Card Payments
65
65
66
66
The following describes the end to end use case with an option to save credit card:
67
67
@@ -83,7 +83,7 @@ The following describes the end to end use case with an option to save credit ca
83
83
84
84
**Note:** Saved Card feature is supported only during checkout
- Before Payment Widget is rendered available payment methods are retrieved from SSE `/ccstorex/custom/isv-payment/v2/paymentMethods` endpoint. Saved credit cards are also retrieved from OCC in case user is logged-in.
193
193
-`Card` component renders by default list of saved cards if it is not empty and user is logged-in. Otherwise credit card form is rendered
194
194
- Credit card form is managed by `IsvCheckoutCardDetails` component. Saved cards are managed by `IsvCheckoutSavedCards` component. Shopper can switch between both components to choose preferable way to pay.
195
-
-FlexMicroform is initialized by fetching keys from SSE using `/ccstorex/custom/isv-payment/v2/keys` endpoint
195
+
-Microform is initialized by fetching keys from SSE using `/ccstorex/custom/isv-payment/v2/keys` endpoint
196
196
- Transient token is generated client side and is then included into payment details during order submission
197
197
- In case shopper pays with saved card only savedCardId is sent and transient token is not generated. Shopper can also choose to set card as default
The list of handlers processing credit card Webhook requests in SSE can be found in `server-extension/src/services/payments/index.ts`
207
207
@@ -227,7 +227,7 @@ The list of handlers processing credit card Webhook requests in SSE can be found
227
227
Consume authentication is supported through the means of [Cardinal Cruise](https://cardinaldocs.atlassian.net/wiki/spaces/CC/overview?mode=global) integration. According to documentation:
228
228
> If you are using tokenization, you must use the Direct integration method.
229
229
230
-
Considering FlexMicroform is based on credit card tokenization and same is applicable to saved credit cards the Direct integration method has being considered for implementation. Please refer to the following documentation on how Direct integration method works:
230
+
Considering Microform is based on credit card tokenization and same is applicable to saved credit cards the Direct integration method has being considered for implementation. Please refer to the following documentation on how Direct integration method works:
231
231
232
232
-[Cybersource Payer Authentication using Simple Order API](https://developer.cybersource.com/library/documentation/dev_guides/Payer_Authentication_SO_API/Payer_Authentication_SO_API.pdf)
@@ -243,7 +243,7 @@ Payer authentication is enabled by default using `payerAuthEnabled` gateway sett
243
243
Generally payer authentication services are executed together with credit card authorization:
244
244
245
245
1. PayerAuth setup is created using card information using `/ccstorex/custom/isv-payment/v2/payerAuth/setup` SSE endpoint
246
-
2. Credit card is tokenized as per process described in the [FlexMicroform Card Payments](#flexmicroform-card-payments) section
246
+
2. Credit card is tokenized as per process described in the [Microform Card Payments](#microform-card-payments) section
247
247
3. Order is created and "Authorize" Webhook request is triggered
248
248
4. Credit card Authorization service is called along with Payer Auth Enrollment
249
249
5. In case credit card is enrolled in payer authentication, authorization is rejected with specific reason code (10000). The response from payment provider will contain all data needed to start consumer authentication flow in storefront
Copy file name to clipboardexpand all lines: packages/payment-gateway/gateway/isv-occ-gateway/config/locales/en.json
+1-1
Original file line number
Diff line number
Diff line change
@@ -62,7 +62,7 @@
62
62
"googlePayMerchantNameHelpText": "Merchant name encoded as UTF-8. Merchant name is rendered in the payment sheet. In TEST environment, or if a merchant isn't recognized, a “Pay Unverified Merchant” message is displayed in the payment sheet",
0 commit comments