Credit Card Payments

Subscribe vaults customers credit cards for you allowing you to be PCI compliant while storing the payment method details in Vindicia’s servers in an encrypted form. Security and compliance are always crucial considerations even more so when it comes to subscriptions as the customer’s payment method is stored for recurring processing. Vindicia offers the highest level of security: PCI-DSS v3. Using Subscribe, you never store payment information within your servers, which drastically reduces your compliance burden. Vindicia handles all compliance requirements for you by providing iframes (credit card fields) that receive payment data and store it in a tokenized/encrypted form on our servers. iframe fields provide a merchant branded seamless payment experience for your customers. For more details, refer to Payment Method Tokenization in the Subscribe Feature Implementation Guide. When Subscribe vaults the credit cards for you through iframe, you accept and process customer payments by submitting that data directly from your order form to Vindicia over Secure Sockets Layer (SSL). As a result, you can create a storefront that accepts and stores credit card information without ever loading it into your own database. Vindicia offers 2 solutions for secure handling of payment methods:

• Payment Method Tokenization (PMT) is used in conjunction with Subscribe’s REST API.
• Hosted Order Automation (HOA) in use for Subscribe’s SOAP API.

​

Billing Statement Identifier

The Billing Statement Identifier field enables merchants to define the line of text that will appear on their customers’ credit card statements, in association with the related charge. This identifier must be discussed with the payment provider to meet specific format requirements. The Billing statement identifier can be defined on the Billing Plan/Product and the input appears as an identifier on the Customer’s credit card statement. For example, website.com|3101231234. For one-time charges, the billing statement identifier should also be defined.

​

3DS/PSD2 Authentication

3DS/PSD2 Authentication is relevant for merchants within/selling within the European Economic Area (EEA). It is a directive to implement a two-factor authentication payment standard called 3D Secure (3DS) for credit card payments. 3DS provides a software protocol ensuring issuing banks can authenticate the customer making a purchase and validate the customer’s identity as the owner of the credit card. This means that a customer may need to be redirected for an identity authentication challenge that may take the form of request for an SMS (text) code or a fingerprint. In a subscription scenario, the challenge (if required) would take place at the initial payment for the subscription and would not be required for recurring purchases. For more details, see our 3DS regulation article Parent topic:Subscribe Payment Support