Payment data issues

[AdrianoLMRS]

Issue: Handle Reservation Form Data with Cache and MongoDB Integration

Description

After the user completes the reservation form in public/reserva.html, the following flow should be implemented:

1. Cache Storage:

   • The form data needs to be stored in a cache after submission.

2. Payment Confirmation:

   • If the payment is confirmed, the cached data should be stored in the Reservation collection in MongoDB.

3. Payment Decline:

   • If the payment is declined, the cached data should remain stored.

4. User Experience:

   • If the user revisits reserva.html, the form should automatically populate with the previously cached data.

Expected Behavior

• The user's form data is cached immediately after the form submission.
• The system integrates with the payment gateway to detect the payment status.
• Based on the payment outcome:
  • Success: Move the data from the cache to MongoDB.
  • Failure: Keep the data in the cache for future user convenience.
• When revisiting the form, pre-fill it with cached data.

Requirements

• Technologies:
  • MongoDB for storing confirmed reservations.
  • A caching mechanism (e.g., Redis, in-memory storage, or a similar solution).
• Frontend Behavior:
  • Retrieve and populate cached data in reserva.html.

Tasks

1. Implement a caching system to temporarily store the form data.
2. Integrate with the payment gateway to handle confirmation/decline.
3. Implement logic to move cached data to MongoDB upon payment confirmation.
4. Ensure form pre-fill functionality using cached data.

Additional Notes

• Discuss and decide on the caching technology to be used.
• Ensure data consistency between the cache and MongoDB.
• Handle edge cases, such as cache expiration or partial data scenarios.

[AdrianoLMRS]

Site need user authentication first, maybe Cookies or WebAuthn sessions be the right choice

Issue : #3