Status
Is Payerworks working right now?
Each part Payerworks runs is measured every five minutes from outside it. This page says what the last measurement found, how the calendar month has gone so far, and what a person at Payerworks wrote about any incident.
Measured every five minutes
The parts Payerworks runs
Reading the latest measurement.
Payerworks publishes what it measured. It makes no uptime promise on this page.
Written by a person
Incidents
An incident is what a person at Payerworks writes about a problem: what is affected, what is known, and when it was resolved. A failed measurement alone is not an incident.
The method
How it is measured
Every five minutes a small function of its own calls the API’s health route and a sandbox claim over the public internet, the way a customer does, fetches this site’s home page, and reads the webhook worker’s state and its own failures. It stores one row per part per five minutes and nothing a customer sent.
A part counts as answering only when it answered what it should, in five seconds. A part that could not be measured (no test key set for the sandbox yet, a metric that could not be read) is said as not measured, and is counted neither way.
A month is the calendar month in UTC, from its first day or from the first measurement, whichever is later. A percentage is shown only after an hour of measurements, and it is cut, never rounded up.
This page and its two files are served apart from the API, so they still answer when the API does not.
Payers
Payerworks is connected to no payer yet, so no payer is measured or listed here. When a payer connection opens it is added as its own part.
Talk to us
What happens next
- 1
A person at Payerworks reads what you sent, usually within a business day.
- 2
One reply by email names the next step: our trading partner details, where each of your payers stands, or a key for the API.
- 3
Nothing follows unless you answer. There is no sequence behind this form.
Or write to hello@payerworks.com.