{"id":317,"date":"2017-05-24T13:03:57","date_gmt":"2017-05-24T18:03:57","guid":{"rendered":"https:\/\/easydigitaldownloads.com\/development\/?p=317"},"modified":"2021-12-15T15:30:58","modified_gmt":"2021-12-15T21:30:58","slug":"stripe-gateway-2-6-beta-and-recurring-payments-adds-support-for-existing-cards","status":"publish","type":"post","link":"https:\/\/easydigitaldownloads.com\/development\/2017\/05\/24\/stripe-gateway-2-6-beta-and-recurring-payments-adds-support-for-existing-cards\/","title":{"rendered":"Stripe Gateway 2.6 Beta and Recurring Payments adds support for existing cards"},"content":{"rendered":"

After nearly a month in development, the first beta of version Stripe Gateway 2.6 is available for testing. This upcoming release has quite a few significant improvements along with some bug fixes.<\/p>\n

Existing Cards feature<\/h3>\n

Previously the Stripe Gateway has always required that a customer enter in their full card details in order to complete their purchase. In Stripe 2.6, logged in users will be presented with the ability to select a card they have used on a previous purchase or add a new card.<\/p>\n

\"\"<\/p>\n

Uses will also be able to manage their cards associated with their Stripe account, including adding new cards, setting a new default card, removing a card, or update a card’s billing details. This form is included by default with the edd_profile_editor<\/a> shortcode, but can also be included in a custom integration using the edd_stripe_manage_cards()<\/code> function.<\/p>\n

\"\"<\/p>\n

Because it’s helpful to know if this feature is being used, payments that use an existing card will have a flag set in post meta. We’ve included the ability to see this flag within the View Order Details in the ‘Payment Meta’ metabox, as well as a report in Downloads \u2192 Reports\u00a0\u2192 Stripe Reports. This provides a graph showing the number of times a new card or existing card was used along with the revenue generated by each, to give store owners some insight into how the feature is affecting purchase behavior.<\/p>\n

\"\"<\/p>\n

The existing card feature is only auto-enabled on new installations. When upgrading an existing site, it will need to enabled first. This is to prevent any unexpected display issues on checkout, giving store owners a chance to test it out before using it on their live sites.<\/div>\n
If you are using Recurring Payments<\/strong>, the Existing Cards feature requires you be using Recurring Payments 2.7.1 or later<\/em>.<\/div>\n

How does this work?<\/strong>
\nIt’s important to note that the Existing Cards feature in Stripe Gateway 2.6 does not keep\u00a0any credit card information on a store’s server or database. Stripe has an existing API that allows\u00a0us to request the payment methods of an existing Stripe customer record. Since\u00a0the Stripe and Recurring Payments extensions\u00a0for Easy Digital Downloads keep\u00a0this Stripe customer ID associated with the EDD Customer record, we can retrieve it for\u00a0users who are authenticated into their accounts. Full card details are not available via this API,\u00a0and neither the full card number nor verification code (CVC) can be accessed. This data is securely stored on the Stripe servers.<\/p>\n

Statement Descriptor setting<\/h3>\n

Easy Digital Downloads has previously used a combination of the products purchased and\/or store name to determine what the statement descriptor, which is what charges from the store look like on a customer’s bank statements. In version 2.6, we’re adding the ability to define a Statement Descriptor to help customers easily identify charges from a store. This setting also comes with an email token so a customer can be informed of what the charges will look like in their purchase receipts.<\/p>\n

\"\"<\/p>\n

Auto-complete attributes<\/h3>\n

When inputting\u00a0card details into the checkout form, Stripe Gateway now fully supports the standard autocomplete attributes, allowing customers to use payment methods they have stored in their browser’s form fill tools, or other programs that securely store their card data.<\/p>\n

Stripe Radar support<\/h3>\n

Radar is Stripe’s built in fraud prevention tool. It gives account owners the ability to define rules for payments that present risk to the store in the form of fraudulent purchases. If a payment via Stripe triggers a rule that allows the charge, but presents the store owner to review it, the Stripe Gateway extension will add a payment note stating that it was flagged for review. It will also add a payment note if a payment has been manually approved after it’s been reviewed.<\/p>\n

Additional enhancements<\/h3>\n