An ASB card decline at a checkout can leave two separate questions: has the service problem been resolved, and what happened to my particular purchase? The first can be answered by an incident update. The second needs the transaction record, the merchant's information and, where necessary, help from the bank. A general recovery notice cannot settle every individual account question.
This guide was researched on 27 October 2026 in Bangladesh, when it was already 28 October in New Zealand. It explains the published incident status and a practical way to organize an uncertain payment. It does not diagnose an individual account, guarantee a refund or provide a live monitoring service. Check the linked official pages for any later change.
What the payment provider confirmed
Cuscal Paymark's incident page for ASB Visa declines recorded an investigation update at 20:11 NZDT on 27 October. It said ASB was investigating transaction declines and warned that contactless card and mobile-device payments might fail, with insertion or swiping described as an alternative during that incident. At 20:37 NZDT, Paymark reported that a fix had been implemented and the incident was resolved. [Paymark incident record](https://status.paymark.co.nz/incidents/1z0s1g804jdn).
That is the scope of the verified notice. It does not establish a cyberattack, a loss of customer funds, the number of people affected or the exact cause. It also does not prove that every later declined transaction has the same explanation. Those stronger claims would need their own evidence.
When sharing the update, include the date and time zone. A screenshot saying “resolved” without its incident title can be misleading when several services have separate notices. Keep the direct incident link rather than relying only on a status homepage, whose headline may change as new events occur.
Separate the service status from your purchase status
Start by writing down what you actually know. Did the terminal display a decline? Did the merchant issue an approved receipt? Does your account show a pending entry, a completed entry or nothing you recognize? These observations are related, but they are not the same record and should not be collapsed into one conclusion.
For example, a fictional shopper might remember a failed tap, then use another payment method successfully. Later they notice an entry associated with the first attempt. The useful next step is to compare the amounts, times and receipts. It is not to assume immediately that the merchant deliberately charged twice or that the bank has permanently taken extra money.
Keep each attempt on its own line. Label the method used and the outcome reported at the time. If you are unsure, write “unknown” rather than filling the gap from memory. A short, accurate sequence is easier for a support team to investigate than a long description that mixes several attempts together.
This record is for your private use and for the appropriate support channel. Do not post an unredacted banking screenshot in a public discussion. An account problem can be described without exposing balances, account identifiers, card details or unrelated purchases to strangers.
What a pending entry means
ASB's help page explains that card purchases can reduce the available balance while they are still awaiting merchant processing. It also describes pre-authorisations, such as a temporary holding amount associated with a service before the final payment. The page says processing times can vary. A pending entry therefore needs to be read according to its status, rather than automatically treated as a completed charge. [ASB pending transactions](https://www.asb.co.nz/help/pending-transactions-on-my-credit-card.html).
In your notes, copy the status exactly as shown. “Pending” is useful information; replacing it with “money stolen” changes an observation into an unsupported allegation. Equally, do not dismiss an unfamiliar pending entry simply because it has not completed. If you suspect an unauthorized transaction, use the bank's urgent fraud route.
A hypothetical example helps with the bookkeeping. Suppose a purchase is for NZ$42 and you can see one pending entry for NZ$42 plus a receipt showing a different method was accepted. You have two pieces of evidence to reconcile. You do not yet have enough information to conclude what the final account position will be.
Avoid calculating your final loss by adding every temporary entry to every completed payment without checking their status. Keep a working list, then update it as the bank and merchant clarify the records. This is an organizational method, not a prediction that a particular entry will disappear by a promised deadline.
If the card still declines after the notice says resolved
ASB's general card-decline guidance lists several possible explanations, including fraud monitoring, restrictions selected through Card Control, available funds and incorrectly entered information. These are general troubleshooting categories, not findings about your account or explanations of the October incident. The bank's help page directs customers who still have difficulty to its support team. [ASB card-decline help](https://www.asb.co.nz/help/why-would-my-visa-credit-card-or-visa-debit-card-not-work-when-trying-to-shop-online.html).
Begin with a precise description of the remaining problem. Does it happen at one merchant or in more than one setting? Is it a physical card, a mobile wallet or an online purchase? What did the terminal or app actually say? Those distinctions help frame a support request without requiring you to guess the underlying technical fault.
Do not disable a security feature simply to make a payment go through. If a setting appears relevant, review the bank's official instructions and consider whether the setting was intentionally chosen. An unexpected decline is a reason to investigate, not a reason to bypass protections or follow an unknown person's instructions.
If you need to complete a purchase, discuss an accepted alternative with the merchant and confirm the status of the earlier attempt first. Avoid repeatedly making the same attempt without understanding the response. This guide cannot tell you which method will work at a particular terminal or whether a particular payment has been approved.
Keep a useful evidence packet
A compact evidence packet can contain the purchase date, approximate time, merchant name, amount, receipt and a brief sequence of attempts. Add any reference supplied by the merchant or bank. Preserve the original documents privately so that you can refer to them accurately if the question remains unresolved.
Make the chronology factual. For example: “At about 8:15 pm, the terminal displayed declined. I then paid using another method. At 9:00 pm, I saw an entry marked pending.” This is a fictional illustration of a clear report. It is more useful than “everything was broken and I was charged twice” when the final status has not been established.
Separate what you want from what you know. Your request might be confirmation of the transaction status, an explanation of an unfamiliar entry or investigation of a possible duplicate. Stating that request clearly helps the recipient understand the problem. It does not require you to assert a technical cause or legal entitlement.
Keep a record of the response as well: who you contacted, when, the reference number and the next step they gave you. If you contact another support channel later, the record can prevent the same issue from being described differently each time. Do not include passwords, PINs or verification codes in this packet.
Use the bank's dispute route when appropriate
ASB's dispute page recommends checking transaction details and considering whether an authorized household purchase or subscription explains an unfamiliar entry. It asks for the date, amount, reason for disputing and supporting receipts or communications. The page distinguishes ordinary pending-transaction processing from suspected fraud, for which it says to contact the bank immediately. A successful recovery is not guaranteed. [ASB transaction disputes](https://www.asb.co.nz/banking-with-asb/transaction-dispute.html).
For a purchase you recognize, the merchant's receipt and records may help clarify what was accepted. Ask a specific question, such as whether the earlier attempt was approved in their system. Keep the reply with your other evidence. Do not assume that a cashier can determine the bank's final processing state merely by looking at your phone.
For something you did not authorize, treat that as a different problem from an inconvenient decline. Follow the bank's fraud guidance promptly. A public outage notice should not be used as a reason to ignore suspicious account activity or to wait for a stranger in an online discussion to decide whether it matters.
When a support team gives a timeframe, note the conditions attached to it. A general help-page estimate is not a personal guarantee for a complex case. If the agreed next step does not occur, follow up with the reference and the earlier response rather than starting again with an incomplete description.
Be cautious about messages claiming to fix the outage
ASB's Scam Hub warns about impersonation and says it will not ask for banking passwords, PINs or verification codes. It also warns against requests for remote device access or changes to phone settings. The bank lists its fraud team as available around the clock on 0800 272 372 in New Zealand, or +64 9 303 0332 from overseas. Verify contact details through the official site when you need them. [ASB Scam Hub](https://www.asb.co.nz/banking-with-asb/online-security.html).
An unexpected message may sound convincing because it mentions a real event. Knowing that an outage occurred does not prove the sender is the bank. Treat the message's identity and its claims as separate questions. Use a route you independently know, rather than trusting a link or callback number supplied by an unknown sender.
This is especially relevant when you are tired, embarrassed at a checkout or eager to finish a purchase. A promise of an immediate fix can feel helpful. Pause long enough to check the destination and the request. A legitimate service problem does not justify handing over credentials to someone who approached you unexpectedly.
If you think you have already disclosed sensitive information, use the bank's urgent help route. Do not rely on deleting the message or blocking the sender as proof that the account is safe. Explain what happened through the verified channel so the bank can advise on the appropriate account-specific response.
A simple checkout plan for another disruption
Think about a fallback before you need it, using options you already have and can manage safely. That could mean carrying an existing physical card when you normally use a phone, or knowing how you would postpone a nonessential purchase. It does not mean opening a new account, borrowing money or buying a service because of this article.
For a household, agree who will keep the receipt and who will check an uncertain transaction. Otherwise two people may separately contact support with different versions of the same purchase. A shared note can help, but keep sensitive account information in an appropriately private place rather than an open group conversation.
For an important planned payment, check the recipient's accepted methods and the bank's current service information in advance. If a problem occurs, communicate with the recipient through an established channel. A screenshot of an attempted transfer is not a substitute for the recipient confirming that payment has arrived.
The goal is to reduce confusion, not to promise that every payment system will always be available. A small amount of preparation can make it easier to decide whether to wait, use an agreed alternative or seek help. The decision still depends on your own circumstances and the actual status of the transaction.
Conclusion
Paymark marked the identified ASB Visa incident resolved. For a customer left with an uncertain purchase, the next useful task is reconciling the individual records: terminal response, receipt and account status. Keep those facts separate, use official support for unresolved questions and treat suspected unauthorized activity urgently. A clear record is more helpful than guessing from an outage headline.
Sources and research note
The Paymark incident page was read directly in the browser during research on 27 October 2026 UTC, already 28 October in New Zealand. ASB's linked help, dispute and security pages were checked during the same research session. Examples are fictional and provide no account-specific financial or legal determination. No root cause, customer count or compensation entitlement is asserted. The header is an original conceptual illustration, not a photograph of ASB equipment or the incident.