Payment outage response

Who Should I Contact When Credit Card Processing Is Down?

Contact the organization responsible for the failing layer. Start by checking whether the problem affects one device, one location, or the provider's wider service. Then route the incident to your network administrator, POS or integration provider, payment processor, gateway, or terminal support team with specific evidence.

First response

Protect transaction records before changing the system

Pause repeated payment attempts until you know whether a transaction completed. Review the payment application, terminal, and provider portal for approved, pending, offline, or uncompleted records. Preserve receipts, timestamps, exact error text, and sanitized transaction references before restarting, signing out, reinstalling software, switching locations, or resetting equipment.

Keep sensitive data out of tickets: never send full card numbers, security codes, PINs, passwords, bank credentials, or secret API keys through email, chat, screenshots, or general support forms.

Choose the right owner

Match the symptom to the team that controls it

A processing outage can begin in the local network, point-of-sale application, device, gateway, processor, or an upstream service. A quick scope check helps avoid sending every incident to the same support desk.

Internet provider or network administrator

Start here when other business systems are offline, multiple payment devices lose connectivity, or a recent firewall, DNS, Wi-Fi, router, or network-policy change coincides with the failure.

POS or integration provider

Contact the POS or software team when the application will not open checkout, a reader will not pair, an integration returns errors, or nonpayment features in the same system are also failing.

Processor or gateway support

Use the support channel listed in the merchant portal, statement, welcome materials, or terminal documentation when authorizations fail across otherwise connected devices or the provider reports an incident.

Terminal program or hardware support

Use the authorized device-support path when one terminal has a model-specific error, physical damage, power failure, or persistent diagnostics that differ from working stations.

Five-minute triage

Determine the outage boundary

Observe the scope

  • Record the exact error and the first known failure time.
  • Check whether one device, every station, or more than one site is affected.
  • Test the approved network with another authorized business device.
  • Check the provider's official status page or authenticated dashboard notices.

Compare the workflow

  • Confirm whether cash sales and nonpayment POS functions still work.
  • Check whether card-present and online channels fail in the same way.
  • Compare the affected terminal with a known-working station.
  • Note any recent software, credential, equipment, or network changes.

Status and connectivity

Separate a provider incident from a local network problem

Provider status pages and authenticated service notices can confirm a known incident, but a clear status page does not prove that the local payment path is healthy. Official terminal documentation shows that DNS resolution, service reachability, signal quality, local connectivity, and hardware state can fail independently. Use built-in diagnostics when available and give the network administrator the current requirements for the exact platform and reader.

Avoid speculative configuration changes: do not open firewall access, disable security controls, or factory-reset equipment without current instructions from the responsible provider.

Continuity decisions

Use only preconfigured, provider-supported fallback methods

Some payment systems offer offline acceptance or alternate connection methods, but availability, limits, upload deadlines, eligible payment types, and merchant risk vary. Confirm that the feature was configured for the specific account, application, and hardware before relying on it. Offline payments may be declined later, and pending records can be lost after disruptive account or device actions.

If offline acceptance is already approved

  • Follow the provider's current instructions and risk settings.
  • Tell staff how to recognize pending offline records.
  • Reconnect and upload within the provider's required window.
  • Reconcile uploaded records before retrying uncertain payments.

If no approved fallback exists

  • Use an established noncard continuity procedure.
  • Do not write down card data for later entry.
  • Give customers accurate, noncommittal timing updates.
  • Document operational impact for the incident record.

Escalation packet

Send details that shorten the support handoff

Include the merchant account or location identifier used by the authorized support channel, device model and asset identifier, application and software versions, connection type, exact error, timestamps with time zone, affected locations and channels, official status-page observation, diagnostic results, recent changes, and steps already attempted. Use sanitized transaction references rather than card data.

Common questions

Payment outage contact FAQ

Should I call the cardholder's bank?

Not for a broad merchant outage. The cardholder may contact the issuer about an individual decline, while the merchant should route system-wide failures through its network, POS, gateway, processor, or terminal support path.

How do I find my processor's support number?

Use the authenticated merchant portal, recent statement, onboarding materials, or approved device documentation. Avoid phone numbers from unsolicited messages or unverified search results.

Should I keep retrying a payment?

No. First check transaction history and pending or uncompleted records so an uncertain response does not become a duplicate charge.

Can I take card details on paper?

No. Use only an approved continuity method. Do not record sensitive authentication data or full card information for later processing.

Last editorial review: August 12, 2026. Sources reviewed: current official Square outage and offline-payment guidance and Stripe Terminal network documentation.

Next step

Route the incident with evidence

Protect pending records, identify the affected layer, and contact the provider that controls it with timestamps, scope, diagnostics, and sanitized references.

Contact Payments Max

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US