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
Navigate to Merchant Tools / Site Preferences / Custom Preferences.
You can require a 3D Secure authentication for payments by setting this feature to Yes.
3-D Secure Min. Limit
Set a limit which, if exceeded, triggers a 3D Secure authentication: Consumers are asked to enter their password/secret to authorize the transaction. Precondition: Enable 3DS is set to Yes.
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 (as configured in the General Settings) and the order number.
To modify the descriptor, check the script:
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.
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 custom order attribute paymentGatewayOrderState 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 custom order attribute paymentGatewayOrderState will be labeled as Processing.
The type of that preference is "set-of-string". It allows the configuration of conversion rates relative to the default currency of the current site. As visible in the screenshot above the structure of each entry is
ISO-3 currency code":"Number", e.g.
Precondition: Enable 3DS is set to Yes.
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.
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
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 custom order attribute paymentGatewayOrderState will be updated to status Canceled.
2. Capture: Triggers transaction type capture-authorization. The payment will be captured/invoiced, and the corresponding custom order attribute paymentGatewayOrderState will be updated to status Processing.
3. Refund: Triggers transaction type refund-capture. The payment/invoice will be refunded, and the corresponding custom order attribute paymentGatewayOrderState 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 custom order attribute paymentGatewayOrderState 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 cartridge but only in Salesforce order management.