Moolah - Known Issues / Observations

Owned by Nadine Burroughs
Last updated: Jul 17, 2023
2 min read

This document outlines known issues, outstanding items, or extra notes as they relate to the Moolah/ThreeStep payment configuration.

Known Issues

Duplicate Payment Race Condition

This is a race condition that is similar to the same known issue for the AuthNet/ThreeStep payment configuration, however, this issue is significantly more difficult to reproduce within AuthNet (see https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3099656228/Known+Issues+Observations#Duplicate-Payment-Race-Condition). In both configurations, the window of time to reproduce this issue is still very small (within a few seconds or less).

When making the same payment in two separate sessions (i.e. within two separate browsers, devices, etc.), it is possible to make a duplicate payment. The setup to have this issue occur requires that payment towards the same payment attribute is made within separate sessions at almost the same time (within a few seconds or less of one another).

User Not Redirected to Post-Processing Error Page (11.0.1, 11.0.2, 11.1.0)

There are no client sites that are on version 11.0.1, 11.0.2, or 11.1.0 that use the Moolah/ThreeStep payment configuration.

In the early LTS and innovation 11-series version releases, user’s were not redirected to the post-processing error page when a post-processing error occured after payment. Instead a UE is thrown. This occurs with the Moolah/ThreeStep payment configuration, and was resolved in version 11.0.3 under case https://heuristicsolutions.atlassian.net/browse/LB-2723.

Unhandled Exception Thrown After Recycling App Pool

Only reproducible in specific test environments, but will the belief that certain conditions could cause this error to occur in real production sites. See https://heuristicsolutions.atlassian.net/browse/LB-2743 for more information.

It’s possible for a UE to be thrown during the payment process when the app pool is recycled right before a user completes their purchase. The payment itself is taken successfully. This error only seems to occur under very specific circumstances and is unlikely to happen in a production environment.

Observations

Payment Gateway does not check credit card expiration date

The Moolah Payment Gateway does not check whether the credit card entered for payment has a valid expiration date.