Credit Card and Maestro SecureCode
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.
Maestro SecureCode is a debit card by Mastercard, which is processed as Credit Card payment.
Credit Card Configuration
To configure your Credit Card payments, please contact Wirecard Support. Available Credit-Card-specific settings are listed below.
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 app 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 app settings.
3-D Secure Only
You can also require 3-D Secure for all payments. 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.
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 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 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, contact Wirecard Support.
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.
Enable this feature to send the descriptor with each request/response.
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.
Post-processing operations, such as refund, are currently not supported by the Wirecard Shopify App. Use the Wirecard Enterprise Portal (WEP) to execute post-processing operations.