FAQ
Common questions about integrating with the Paystand X public API.
Navigation
- Guides — integration patterns (ERP sync, fees, polling)
- API Reference — REST endpoints grouped by domain (customers, accounts receivable, payments, fees, payouts)
- Webhooks — event payloads and setup
- Chaining IDs across API calls
- What the public API does not support today
- Webhook and REST polling matrix
Which environment should I use?
Use Sandbox (https://api.paystand.co/v3) for development and Production (https://api.paystand.com/v3) for live ERP sync. Credentials are not interchangeable.
Do I need webhooks?
No. Webhooks are recommended when your stack can receive HTTPS callbacks. Otherwise, poll list endpoints with date filters — see the query guide.
Can I delete a receivable or customer via API?
- Customers: There is no public DELETE for payer customers. Create and update only.
- Receivables: Void invoices with Cancel Receivable. Hard delete is not supported for partner integrations.
- Attachments: You may remove PDF attachments from a receivable without voiding the invoice. This deactivates the attachment (no longer downloadable); it is not a hard delete of the receivable or a guaranteed purge of the stored file.
Where are date filters documented?
See Query and incremental sync. Remember: /receivables/read does not support f.querytype=by-query-filters; use GET /receivables instead.