Credit and debit cards are one of the most popular payment methods worldwide. They allow the consumer (aka cardholder) to buy goods and services using a (virtual) card.

1. Select WooCommerce/Settings.
2. Click the Payments tab.
3. Scroll down to Card Payments.
4. Click either Card Payments or the Set up button (on the right) to open the configuration page:

Depending on the order value, you might consider reducing payment risks and keeping the payment process simple. Therefore, the extension allows configuring non 3D Secure and 3D Secure limits.

The limit settings here need to match the limit settings defined in your acquirer contract. Acquiring contract settings may not be overruled by extension settings.

The following six examples assist you in setting the limits according to the order value:

You can also require 3D Secure for all payments by entering only your 3D Secure MAID and 3D Secure Secret Key. The MAID and Secret Key fields remain empty:

In this case, the 3D Secure limits set are not considered, and all payments are processed with 3D Secure.

Card Payments can be performed using two different payment actions:

1. Authorization: Payments for orders are not captured/invoiced but only authorized by the consumer, and therefore only reserved. For debit, you have to confirm/capture the amount manually.

• This payment action triggers the transaction type authorization for payment method Card Payments.
• The order created in WooCommerce order management will be labeled as Authorized.

2. Purchase: Set payment action to Purchase to invoice payments of orders automatically.

• This payment action triggers the transaction type purchase for payment method Card Payments.
• The order created in WooCommerce order management will be labeled as Processing.

Use this feature to set your preference whether or not each card transaction should be subject to Strong Customer Authentication (SCA).

The Payment Services Directive 2 (PSD 2) aims to reduce fraud in the European e-commerce sector. It makes SCA mandatory for consumer-initiated online payments.

Available options:

• No preference (default).

• No challenge requested: Select this option if you do not want to request SCA for each card transaction. Selecting this option may lead to a higher conversion rate, but could also increase the probability of fraud.

  No shift of liability takes place.

• Challenge requested: Select this option to request SCA for each card transaction. Selecting this option may help to reduce fraud, but could also lead to a lower conversion rate.

The descriptor is the text representing an order on the consumer's bank statement issued by their card company. It provides information for the consumer, as it associates a specific debit on the consumer's account with the respective purchase in your shop.

• If the descriptor is Disabled, the issuer/acquirer generates a default entry for each purchase.

• If the descriptor is Enabled, the default descriptor text consists of the first 9 characters of the shop name and the order number.
  To modify the descriptor, use the method create_descriptor in the file woocommerce-credit-agricole-ee/credit-agricole-woocommerce-extension/classes/helper/class-additional-information.php.

  Data and Structure:

  • Your merchant name and merchant location are usually displayed on the cardholder's bank statement (static data). These fields, or parts of them, are used for presenting the dynamic data on the cardholder's statement.
    Apart from such static data, you can add transaction information to better reference your sales. For example, you can use invoice number, booking ID or transaction ID. This data is typically passed along to you (the merchant). As the field has a fixed length, the longer the merchant name, the smaller the number of digits allocated to dynamic information, e.g.:

    • VISA: Name: 25 digits, location: 13 digits
    • Mastercard: Name: 22 digits, location: 13 digits
    • JBC: Name: 25 digits, location: 13 digits

  • Consider all these parameters before setting a dynamic descriptor because any text exceeding the permissible length is cut off and discarded.

  • Be aware that industry-specific restrictions apply depending on card schemes.

  • Note: It is up to the issuer to decide which data provided in the dynamic descriptor is printed on the cardholder's statement. Therefore, Crédit Agricole cannot guarantee that the dynamic descriptor data is fully printed on the cardholder's statement.

  • Crédit Agricole Bank receives the transaction data from the Crédit Agricole processing platform, looks up the merchant address, consolidates static address details and dynamic sales data (including merchant name and merchant location) and routes the information and the settlement request to the issuer. The amount of information that will later appear on the consumer's card statement may vary from issuer to issuer.

Enable this feature to send the descriptor with each request/response.

If this feature is Enabled, additional data will be sent for the purpose of fraud protection. This additional data includes billing/shipping address, shopping basket and descriptor.

Note: The additional information includes the descriptor even if the descriptor option is set to Disabled.

The Crédit Agricole WooCommerce Extension supports recurring payments, which allow consumers to check out without having to reenter their card details.

If this feature is Enabled, consumers will be asked to save their card details for later use (recurring payments, one-click checkout):

Card Payments will be listed as one of the available payment methods the next time the consumer proceeds to the checkout. Card details do not have to be modified and can be deleted at any time.

To access post-processing operations, go to Crédit Agricole Payment Gateway to open the transaction table which lists all successful transactions:

Click a Transaction ID to open the transaction detail view. It shows all available post-processing operations, e.g.:

Depending on your Payment Action settings, there are different post-processing operation workflows for Card Payments:

1. Cancel: Triggers transaction type void-authorization. The payment will be canceled/voided, and the corresponding order in WooCommerce order management will be updated to status Canceled.

2. Capture: Triggers transaction type capture-authorization. The payment will be captured/invoiced, and the corresponding order in WooCommerce order management will be updated to status Processing.

3. Refund: Triggers transaction type refund-capture. The payment/invoice will be refunded, and the corresponding order in WooCommerce order management will be updated to status Refunded.

4. Partial-Refund: Triggers transaction type refund-capture. This post-processing operation can be triggered in the WooCommerce order management as described in WooCommerce Refund Workflow.

1. Refund: Triggers transaction type refund-purchase. The payment/invoice will be refunded, and the corresponding order in WooCommerce order management will be updated to status Refunded.

2. Partial-Refund: Triggers transaction type refund-purchase. This post-processing operation can be triggered in the WooCommerce order management as described in WooCommerce Refund Workflow.

---

Please be aware that stock management is not included in the post-processing operations triggered in the Crédit Agricole extension but only in WooCommerce order management.