@autobusal/order-process 1.3.3 → 1.3.5

package/CHANGELOG.md

@@ -1,9 +1,23 @@
 # Changelog
 
+## 1.3.5
+
+### Fixed
+
+- **A refused funds payment spun forever.** The standard (funds/reserve) processor had only a success branch, so an agent's "not enough funds" left the page on "Processing your order" with no message and the order stuck reserved. It now surfaces the API's own message and returns the buyer so they can try again. (Platform audit BOOK-05-c.)
+
 All notable changes to `@autobusal/order-process` are documented here. This
 project adheres to [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.3.4] - 2026-07-30
+
+### Fixed
+
+- **`noIndex` never used on the order processing page (`OrderProcess.tsx`).**
+  Same rationale as order-confirm - a transient, hash-gated page with no
+  search value, previously indexable by default.
+
 ## [1.3.3] - 2026-07-24
 
 ### Fixed

package/OrderProcess.tsx

@@ -11,7 +11,7 @@ const OrderProcess = ({ t }: Props): JSX.Element => {
   const { type, hash } = useParams();
 
   return (
-    <Meta title={ t('order_process.title') }>
+    <Meta title={ t('order_process.title') } noIndex={ true }>
       <Content type={ type } hash={ hash } t={ t } />
     </Meta>
   );

package/Standard/Standard.tsx

@@ -1,6 +1,8 @@
+import { useEffect } from 'react';
 import { TFunction } from 'i18next';
-import { Navigate } from 'react-router-dom';
+import { Navigate, useNavigate } from 'react-router-dom';
 import { Inline } from '@autobusal/common';
+import { error as notifyError } from '@autobusal/utilities';
 import { Container } from '../styles';
 import { useMakeStandard } from '../services';
 
@@ -10,8 +12,30 @@ interface Props {
   t: TFunction<'common'>
 }
 
+/*
+ * Edited: Claude - Date: 2026-08-22 (audit finding BOOK-05-c)
+ *
+ * This had only an isSuccess branch, so a refused payment - most visibly an
+ * agent's "not enough funds" - left the page spinning on "Processing your
+ * order" forever, with no message and no way out. The reserved order just
+ * sat there. Now a failure surfaces the API's own message (the funds gate
+ * returns exactly the text the agent needs) and returns them to where they
+ * were, so they can top up and try again - the reservation is still theirs.
+ */
 const Standard = ({ type, hash, t }: Props): JSX.Element => {
-  const { data, isSuccess } = useMakeStandard(String(type), String(hash));
+  const { data, isSuccess, isError, error } = useMakeStandard(String(type), String(hash));
+
+  const navigate = useNavigate();
+
+  useEffect(() => {
+    if (isError) {
+      const message = (error as { response?: { data?: { message?: string } } })?.response?.data?.message;
+
+      notifyError(message ?? t('order_process.error', { ns: 'common', defaultValue: 'We could not complete your order. Please try again.' }));
+
+      navigate(-1);
+    }
+  }, [isError, error, navigate, t]);
 
   if (isSuccess) {
     return <Navigate to={ data } />;
@@ -24,4 +48,4 @@ const Standard = ({ type, hash, t }: Props): JSX.Element => {
   );
 };
 
-export default Standard;
+export default Standard;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/order-process",
-  "version": "1.3.3",
+  "version": "1.3.5",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"