Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 11/11/2019 in all areas

  1. 1 point
    asro2004

    Stripe v3 module for SCA

    I have created a fork of the standard Stripe payments module to provide support for SCA. I tried uploading it to the market place, but it does not seem to be accepting it. A copy of the zip is attached. Stripe SCA Payment module Stripe SCA is a refactored version of the standard Stripe payments to update the Stripe API to v3 and support the SCA process flow. Other than using different Stripe API calls to set up and process payments, the main change is to defer order fulfillment to a web hook called by Stripe after the payment has been authorised. This module is installed as a separate payment method from the standard Stripe module and can be run in parallel. Note that it shares the customer_stripe_tokens table created by the standard Stripe module, and cards saved using the standard Stripe module can be reused by the Stripe SCA module, however, cards stored by the Stripe SCA module cannot be reused by the standard Stripe module. They will be rejected by Stripe with a message 'You cannot create a charge with a PaymentMethod. Use the Payment Intents API instead.' Install Copy the contents of this zip to the root osCommerce folder of your store. Login to the osCommerce Admin page of your store and go to Modules > Payment. - Click on the Install button at the upper right of the page - Choose 'Stripe SCA' from the module list and select Install Module. If you are allowing cards to be saved, add the cards management page: - go to Modules > Content - click on the Install Module button at the upper right of the page - select 'Stripe SCA Cards Management Page' and select Install Module. That will add the 'Manage saved payment cards' link to the customers' My Account page. Configuration The basic configuration of the Stripe SCA module is the same as the standard Stripe module, requiring Publishable and Secret API keys, however as the order fulfillment has been moved to a webhook, you need to add the address of the Stripe SCA webhook at your store to your Stripe account dashboard, and add the webhook signing secret it generates to the Stripe SCA payment module configuration. Login to your account at the Stripe web site, and select Developers > Webhooks - select '+ Add endpoint' at the upper right of the page - set the URL to: https://yourstore.url/ext/modules/payment/stripe_sca/webhook.php - select version as 'Latest API version' - select event 'payment_intent.succeeded' and 'payment_event.payment_failed' - click 'add endpoint' to save the webhook endpoint. Then select the new endpoint URL from the list of end points, and then 'click to reveal' to see the Signing Secret. Copy and paste the text of the signing secret to the Webhook Signing Secret in the Stripe SCA module configuration form. The Stripe SCA module adds a log table, stripe_event_log, to the database, and if you select 'Log events?' in the Stripe SCA configuration, it will record each Stripe API call with the parameters that are passed to Stripe and the response received. As the process flow has changed to use a web hook, the order has to be created in a pending state, and then updated to completed status after the payment has been authorised. Consequently, you need to set the new order status to 'Preparing [Stripe SCA]', and the order status is set to the status the order is to be set to, after the payment is authorised. Technical Notes The current stripe-php library, as at module publish date, has been included in in the module install. Calls to the Stripe library functions have replaced directly sending transactions to the Stripe gateway. You should be able to replace the includes/modules/payment/stripe_sca folder with the complete contents of the stripe-php library when Stripe releases updates to their library. If you do so, set the new API version in includes/modules/payment/stripe_sca.php. The Stripe v3 process flow now requires a PaymentIntent to be created before the payment page is displayed, and a 'data secret' it generates to be included in the HTML form. If a saved card is used, the Stripe customer id and payment method id has to be added to the PaymentIntent. During coding, it was found that a payment method could not be removed from a PaymentIntent, so rather than update the PaymentIntent with a server call as the saved card/new card is selected, the adding of the customer and payment method is deferred until immediately before submitting the payment to Stripe in a Javascript call when the form is submitted. The payment_intent.php server hook is also used to save the value of the 'save card' check box in the PaymentIntent so it is accessible to the webhook called after the payment is authorised. Stripe v3 provides UI elements to collect card details. A 'card-element' element is required for the new card to show card number, expiry and CVC fields, but is also required for saved cards in order to provide a place holder that Stripe can use to display authorisation prompts if required. Consequently, two occurrences of the 'card-element' element were created with the name of each toggled depending on whether a saved card or new card is selected. Otherwise, trying to reuse the same element for both purposes block the authorisation of saved card when the new card details was hidden. All order fulfilment and card saving code has been moved to ext/modules/payment/stripe_sca/webhook.php. Note the DIR_FS_CATALOG constant should be set to a path string, rather than the value dirname($_SERVER['SCRIPT_FILENAME']) . '/' because the includes/modules/payment/stripe_sca.php has a require that references the stripe-php library, and is executed at different locations in the directory structure and fails when the DIR_FS_CATALOG value varies with location. stripe_sca_v1.0.zip
×