Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

asro2004

Pioneers
  • Posts

    34
  • Joined

  • Last visited

  • Days Won

    2

asro2004 last won the day on November 30 2019

asro2004 had the most liked content!

Profile Information

  • Real Name
    Alastair Robertson
  • Location
    Auckland, NZ

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

asro2004's Achievements

  1. Please check the sort order of the totals in Modules ~ Order Totals. If all the totals have the same sort order number, that could cause the totals to be in different sequence under different circumstances, depending on what previous queries mysql had run and how it had managed it's cache. The order totals are saved to the database in includes/modules/payment/stripe_sca.php lines 207-214, with the configured sort order, and the order email totals are output in lines 491-493 of that module. The $order_totals variable is set in checkout_process.php using the output of order_total->process(). That prepares the totals in the sequence in which the totals appear in the database configuration table, record with the configuration_key: MODULE_ORDER_TOTAL_INSTALLED. So the email prepared by the stripe_sca module should have the sub totals in the sequence in the configuration table record, but if the order is reprinted from the administration order screen, the totals could be out of sequence if the sort order had not been set. The customer email should be ok, and the problem only occur when the order is re-printed.
  2. I've updated the module to version 1.0.13 to remove a potential SQL injection and tidy the account saved cards display when there are multiple cards (thanks @Smoky Barnable). @mhsuffolk I'm afraid the current version does not support Apple Pay, etc but looking at the Stripe documentation, it does not look too difficult to add. It just involves adding an extra HTML element to host a 'Payment Request' button which is displayed for certain compatible browsers, and some javascript and server code to support the creation and processing of a 'PaymentRequest' in a similar fashion to the handling of the 'PaymentIntent' in the current version. I'll add it to my list of things to do.
  3. Security issue There can be a security problem for anyone who installed version 1.0.3 of this module, with some obsolete values being left in the configuration table when the modules is updated to a later version. Please run the following SQL to remove the obsolete values: DELETE FROM configuration WHERE configuration_key IN ('MODULE_PAYMENT_STRIPE_SCA_PUBLISHABLE_KEY','MODULE_PAYMENT_STRIPE_SCA_SECRET_KEY','MODULE_PAYMENT_STRIPE_SCA_WEBHOOK_SECRET')
  4. The language files are loaded by the code that loads all the modules: /admin/modules.php for the admin pages, and /includes/classes/payments.php for the checkout pages.
  5. The prompts are declared in includes/languages/english/modules/payment/stripe_sca.php. It's probably best to just copy the ext and includes directories from the install/update and let it replace all the corresponding files in the web site. It should only be necessary to make sure the ownership and permissions of the files allow them to be read by apache/nginx. Check your site's error logs for any PHP errors.
  6. The card details form is generated by Stripe using a placeholder passed to it by the module's javascript in includes/modules/paymant/stripe_sca.php around lines 974-977: var card = elements.create('card', {hidePostalCode: true}); // Add an instance of the card Element into the `card-element` <div>. card.mount('#card-element'); Stripe's documentation about elements: https://stripe.com/docs/stripe-js
  7. Module has been updated to 1.0.12 to fix some issues with the stripe payment amount apparent when used in conjunction with some odler discount modules. Also, a problem with duplicate orders in 'preparing' state being created when the customer returns to the cart from the payment page. @peterespana, please use the 'send test webhook...' link in the stripe dashboard to check the link to the webhook on your server. It should show a 400 response code, with the message 'Invalid webhook signature: No signatures found matching the expected signature for payload'. If that is ok, please double check you stripe configuration 'transaction method' is set to 'capture' and not authorise. If that's the problem, it won't send to the webhook until you capture the payment in the stripe dashboard.
  8. @mhsuffolk, @raiwa, @John P, @peterespana I've fixed the order totals missing form the customer email, and the error that occured when a number of items were ordered. I removed the cart items from the Stripe transaction metadata. The marketplace module has been updated with version 1.0.11, and this one includes the correct version number in the app signature.
  9. I have fixed a couple of issues where stripe errors were not being shown to the user. Nothing else changed from 1.0.9 The market place app has been updated to 1.0.10.
  10. 1.0.8 has been uploaded to the market place. It fixes missing customer emails, and order status history information. If would be a good idea to copy the entire contents of the ext and includes folders in the update to the corresponding folders of the store to ensure that all files get to the right places.
  11. Thanks, they have been fixed in 1.0.7
  12. I'm pretty sure the problem is something in the checkout_confirmation.php form. Raiwa had provided some refactoring to the handling of order processing, moving it from the webhook to the payment module, so I took the opportunity to re-check the javascript in the checkout-confirmation.php page, and removed some redundant fields and a dependency on a specific class name on the button. It was possible that a custom theme may disrupt the completion of the payment process, so this could fix it if that was the case for you. I reset the configuration and re-installed the module from scratch on a standard system, and then re-run tests for new cards, saving a new card, and using a saved card, and all worked ok. Please download and install the latest version 1.0.7 from the market place. All files should be replaced. If still no luck, please PM me a copy of the page source of checkout_confirmation.php page.
  13. Is that the 'Manage save cards' in the my account page? Please check your PHP or Apache/Nginx web site log for any errors. The account page is loading the code from includes/modules/content/account/cm_account_stripe_sca_cards.php, with the English text from includes/languages/english/modules/content/account/cm_account_stripe_sca_cards.php
  14. @peterespanaWere you able to see the stripe_event_log mysql table in your store database? It should create a row with the 'action' 'page create intent', and a request something like: {"amount":"7500","currency":"USD","setup_future_usage":"off_session","capture_method":"automatic","metadata":{"customer_id":"26","order_id":"2640","company":"","product_1_name":"Grillage for 6 beam 3 span bridge","product_1_model":"","product_1_id":"72{6}14","product_1_qty":"1","product_1_price":"75.0000","product_1_tax":0}} and the response should be the payment intent object returned by stripe, or an error message. You should see a line in the response 'client_secret', and it is that value that is placed in a hidden field in the payment form by the code in the confirmation function of stripe_sca.php. With the error message you are getting, would suggest an error response from Stripe when the intent is created, but your Stripe log shows a response code 200. Try looking in your PHP error log, or Apache/Nginx log, or check the browser console for any javascript error. Have a look at the page source of the checkout_payment.php page, and search for id="secret". The value of that field should be the client secret returned by Stripe in the payment intent object.
  15. It's probably easiest to just overwrite all of them.
×
×
  • Create New...