Credit Card

Credit Card is one of the most popular payment methods worldwide. It allows the consumer (aka cardholder) to buy goods and services using a (virtual) credit card.

Credit Card Configuration

1. Select Shop Settings/Payment Methods.

2. Scroll down to Wirecard Credit Card.
   

3. Click Wirecard Credit Card to open the Credit Card configuration page:
   

Purchase Price From/To

During checkout, the consumer can choose Credit Card only if the total purchase price is within the specified limits. Select the limits according to your Wirecard contract.

Non 3D Secure and 3D Secure Limits

Depending on the order value, you might consider reducing payment risks and keeping the payment process simple. Therefore, the module 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 module settings.

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

3D Secure Only via 3D Secure MAID

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 set limits are not considered, and all payments are processed with 3D Secure.

Non 3D Secure Only via MAID

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

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

One-Click Checkout

Credit Card payments with the Wirecard extension support recurring payments, which allow consumers to check out without having to re-enter their credit card details.

Enable One-Click Checkout

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

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

Allow Shipping Address Change

For security purposes the extension checks if the shipping address of a consumer has changed since their last order.

• If this feature is Enabled, consumers can use their existing credit cards even after their shipping address has changed between orders.

• If this feature is Disabled, consumers will have to re-enter their credit card details if their shipping address has changed between orders.

Descriptor

The descriptor is the text representing an order on the consumer's bank statement issued by their credit 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 set to No, the issuer/acquirer generates a default entry for each purchase.

• If the descriptor is set to Yes, 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 getDescriptor in the file Extend/Model/Payment_Gateway.php.

  • Allowed characters: umlaut, 0-9, a-z, A-Z, , +, ,, -, .
  • Max. length: 27 characters

  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, Wirecard cannot guarantee that the dynamic descriptor data is fully printed on the cardholder's statement.

  • Wirecard Bank (WDB) receives the transaction data from the Wirecard 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.

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

Send Additional Information

If this feature is set to Yes, 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 No.

Delete Canceled Order

If this feature is set to Yes, every time the payment process is canceled before completion of the authorization/purchase, the corresponding order will be automatically deleted from the OXID order management.

Delete Failed Order

If this feature is set to Yes, every time the payment process fails to complete the authorization/purchase successfully, the corresponding order will be automatically deleted from the OXID order management.

Payment Action

Credit Card payment 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 Credit Card.
• The order created in OXID 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 Credit Card.
• The order created in OXID order management will be labeled as Processing.

Challenge Indicator

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

The Payment Services Directive 2 (PSD2) 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 credit 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 credit card transaction. Selecting this option may help to reduce fraud, but could also lead to a lower conversion rate.

Supported Post-Processing Operations

To access post-processing operations, go to Wirecard Transactions 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 Credit Card:

Payment Action Authorization

1. Cancel: Triggers transaction type void-authorization. The payment will be canceled/voided, and the corresponding order in OXID 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 OXID 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 OXID order management will be updated to status Refunded.

Payment Action Purchase

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

You also have the option of partial Refund/Capture. Partial Refund/Capture is possible until the payment has been refunded/captured in full.

---

Please be aware that stock management is not included in the post-processing operations triggered in the Wirecard module but only in OXID order management.