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
- Select System/Configuration/Payment Methods.
- Click Wirecard Credit Card to open the Credit Card configuration page:
3-D Secure Only via 3-D Secure MAID
In this case, the 3-D Secure limits set are not considered, and all payments are processed with 3-D Secure.
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 Magento order management will be labeled as Processing and an invoice can be created to capture this payment.
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 Magento order management will be labeled as Processing and an invoice has been created.
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.
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 up to 9 characters of the shop name and the full order number. The default maximum length is 20. To modify the descriptor, use the method
getDescriptorin the file
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.
Non 3-D Secure and 3-D Secure Limits
Depending on the order value, you might consider reducing payment risks and keeping the payment process simple. Therefore, the extension allows configuring Non 3-D Secure and 3-D 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:
Supported Post-Processing Operations
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 Magento order management will be updated to status Canceled.
2. Invoice: Triggers transaction type capture-authorization. The payment will be captured/invoiced, and the corresponding order in Magento order management will be updated to status Processing.
3. Credit Memo: Triggers transaction type refund-capture. The payment/invoice will be refunded, and the corresponding order in Magento order management will be updated to status Closed.
Payment Action Purchase
1. Credit Memo: Triggers transaction type refund-purchase. The payment/invoice will be refunded, and the corresponding order in Magento order management will be updated to status Closed.
You also have the option of partial Credit Memo/Invoice. Partial Credit Memo/Invoice is possible until the payment has been refunded/captured in full.
For a step-by-step guide to canceling, invoicing and refunding payments, go to our Post-Processing Operations Workflow page.
Please be aware that stock management is not included in the post-processing operations triggered in the Wirecard extension but only in Magento order management.