Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter rishimidha

    (@rishimidha)

    @shameemreza response from Moneris for Woocommerce below.

    We bypass the cart page, where users normally input their shipping address. This is probably where the preload request is originated – after the user inputs their shipping info in the cart page and continues to checkout.

    We instead have them input this info on the checkout page. But in the past, inputting or changing this address at checkout has caused the Moneris costs to re-calculate, as if the preload request is re-sent when the address is updated. This doesn’t seem to be happening anymore. Is there any way to force it if an address is changed?

    Moneris response:

    Hello Rishi,
    
    Thank you for your email. The Moneris Checkout is working as intended, the transaction amount has to be sent in the preload before the form is loaded on the webpage or in a iframe.
    
    The preload is done with the values that are to be displayed on the Checkout form, and a preload is only done once to  generate a ticket which is then used to load the Checkout form in the browser or Iframe.
    
    The Checkout should not be having the preload request sent before those shipping details are confirmed as the Checkout will not update based on you changing the shipping details as a new preload request should have to be sent to create a new instance of Checkout, as this is not a live form, so the details in which you would like to have displayed on the Checkout form need to be sent in the preload request prior to it being displayed in the browser or Iframe.
    
    These are the mandatory values in a preload request
    
    Request fields for Preload request – Required
    
    VARIABLE NAME
    
    TYPE AND LIMITS
    
    DESCRIPTION
    
    store ID
    store_id String

    10-character alphanumeric Unique identifier provided by Moneris upon merchant account set up API token
    api_token String

    20-character alphanumeric Unique alphanumeric string assigned upon merchant account activation checkout ID
    checkout_id String

    30-character alphanumeric (maximum) Identifies your Moneris Checkout configuration; this is given to you when you configure your page in the Merchant Resource Center transaction amount
    txn_total String

    10-character decimal
    Up to 7 digits (dollars) + decimal point (.) + 2 digits (cents) after the decimal point The total dollar amount of the transaction developmental mode
    environment String

    alphabetic
    qa or prod Indicates the stage of development you are sending the request for:

    testing = qa
    production = prod request type
    action String

    alphabetic Type of request being made to Moneris Checkout server. Allowable values:
    preload or receipt
    Thread Starter rishimidha

    (@rishimidha)

    Hi @shameemreza , thanks for your reply. I have done all of the following:

    – Ensured all plugins are updated.
    – Changed to default theme (twenty twenty three).
    – Completed a conflict test by deactivating all plugins except Woocommerce, Conditional Payments, and Moneris.

    None of the above fixed the issue. I should note that this is a new issue, we’ve been using the store for over a year without experiencing this.

    I have filed a support ticket with the Moneris Gateway plugin developers and am waiting to hear back. I have also already opened a support ticket with WooCommerce ([email protected]), and replied to that ticket today with the System Status Report and Fatal Error Logs, since I had not included those when I first opened the ticket.

    I have also included this info below for you in case it helps:

    System Status Report

    Fatal Error Log – 2023-07-17

    Fatal Error Log – 2023-07-15

    Fatal Error Log – 2023-07-13

    Fatal Error Log – 2023-07-12

    Thank you,

    Rishi

Viewing 2 replies - 1 through 2 (of 2 total)