A payment integration connects more than two screens. It may link a customer’s checkout, a payment provider, an order record and the business’s accounting process. For businesses in Albany and the Great Southern, checking what happens when a payment fails is an important part of deciding whether the connection is ready for use.
Use this checklist with the supplier responsible for the integration. It concentrates on evidence, customer communication and staff decisions. Technical recovery actions must follow the actual provider’s documentation and the business’s configuration, rather than a generic instruction to click again.
Check the meaning of every result
- Ask how the system distinguishes a declined payment from an unknown outcome.
- Identify pending, authorised, completed and reversed states where applicable.
- Find which provider record is used to establish the outcome.
- Check whether the order record updates at the same time.
A timeout can mean that a response was not received, even if the underlying request was processed. NAB Gateway’s transaction timeout guidance explains this distinction and the risk of duplicate processing after an unchecked retry. Its technical procedures are specific to that gateway; ask your own supplier how its system resolves uncertainty.
Do not allow a vague failed label to hide several different conditions. Staff need to know whether they should investigate, contact support or invite another payment attempt.
Check the link between payment and order
- Confirm each payment can be linked to the correct order or invoice.
- Check what happens if payment succeeds but the order update fails.
- Check what happens if an order is created before payment finishes.
- Identify who reviews unmatched or conflicting records.
A customer confirmation email, an order number and a payment reference serve different purposes. Ask the supplier to demonstrate how staff trace one transaction across the relevant systems without needing unnecessary access to sensitive payment details.
Where the business offers collection in Albany or delivery elsewhere in the Great Southern, decide which status allows fulfilment to proceed. Do not let a technical acknowledgement accidentally release an order that still requires review.
Check how repeat attempts are controlled
- Ask how the integration recognises a repeated request.
- Check whether a customer refresh or second click creates another payment.
- Find the approved process for investigating an uncertain attempt.
- Confirm who can authorise a retry or correction.
Duplicate protection is a capability to verify, not something to assume because two apps are connected. Ask whether it applies to the business’s current configuration and how staff can recognise that an earlier attempt is still being resolved.
A temporary alternative payment method also needs coordination. Otherwise a customer may pay through the fallback while the original payment later completes. Record both attempts under the same unresolved case until the outcome is clear.
Check what the customer is told
- Read the messages shown for declined, pending and unknown outcomes.
- Check whether an automated email contradicts the screen.
- Provide a genuine contact route for uncertain payments.
- Explain what information helps staff locate the attempt.
Use clear language about what is known. An uncertain outcome should not be described as a confirmed bank decline, and a pending request should not be presented as a completed purchase. Give staff approved wording that avoids promises about refund timing or release of funds they cannot verify.
Ask customers to use the business’s secure, authorised contact process. Do not request full card numbers or security codes through ordinary email or a shared enquiry form.
Check the operating dependencies
- Test the devices and connections used for the actual service.
- Ask about provider outages and maintenance notifications.
- Identify support hours in Western Australian time.
- Keep a clear escalation route when the usual operator is absent.
Business.gov.au’s payment-method guidance notes that reliability can depend on electricity and telecommunications, and that offline operation varies. Do not infer offline capability from a successful office demonstration.
If an interruption affects the integration rather than the payment provider itself, know who investigates the connection. A general supplier status page may not describe the particular link your business relies on.
Keep unresolved cases visible at a shift handover. Record the last verified status, the supplier reference and the next authorised action. A colleague should be able to continue the enquiry without asking the customer to repeat a payment or start the explanation again.
Check failures safely before wider use
- Use the provider’s approved test facilities or controlled demonstrations.
- Include a delayed response and a lost order update where supported.
- Record the expected result and the observed result.
- Resolve material differences before expanding the service.
Do not deliberately misuse live customer details to generate failures. Ask the supplier how it can demonstrate the relevant cases safely and retain enough evidence for an authorised reviewer to understand the outcome.
After testing, assign ownership of daily exception review and reconciliation. A successful payment demonstration proves little about the cases that require human judgement. The integration is more useful when staff can explain an uncertain attempt, prevent conflicting actions and give the customer an accurate next step.