A webhook shows “Network error”
The Already API could not reach your callback. Check that your receiver is listening, its URL includes the expected path, and the API can reach that host.localhost on a hosted API means the hosted server, not your laptop. Use a public HTTPS URL for a hosted integration. A working local GET /health proves only that your own machine can reach the receiver.
A webhook returns 401
Confirm that the receiver uses the signing secret for that exact endpoint, verifies the HMAC over the timestamp plus the raw body, and accepts the v1= signature format. Registration creates a new secret; changing endpoints without updating your secret causes failures.
I submitted an invoice but the business sees no offer
A submission enters review first. Check itsstatus through GET /partner/v1/obligation-submissions and watch for submission.approved or submission.rejected. Approval also requires an eligible business enrollment, payer review, and funding capacity. Contact your Already operator if the record is still pending.
The business accepted, but payment says “processing”
Acceptance requests payment. The status changes after the transfer provider reports completion and Already reconciles it. A transfer may fail or return later. The operator can inspect the payout and provider status; do not send a second transfer solely because the UI is pending.API requests return 401, 403, or 429
Check that the key belongs to the correct environment and partner, has the required scope, and has not been rotated. 429 responses include Retry-After; back off rather than retrying immediately. An allowed browser origin does not replace bearer authentication.
For unresolved integration issues, send your Already contact the request time, endpoint, HTTP status, partner name, and your own external reference. Do not send API keys, webhook secrets, full bank numbers, or sign-in codes.