GET/api/public/access-request/payment-status

Returns which payment providers (PayPal, Stripe) are currently ready/configured for the access request funnel.

The page “GET /api/public/access-request/payment-status — API Reference” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. The form builder supports freely configurable forms with trigger keywords, field types and required-field flags. The feature is covered by end-to-end tests. `GET /api/public/access-request/payment-status` must be implemented as documented on this page. The client needs to follow the declared method, path, authentication model, required fields and error responses rather than copying only the example payload. Zentor has no general developer API-key system; a route is either public or applies the documented Widget token and origin validation. For `/api/public/access-request/payment-status`, evaluate the HTTP status together with the JSON body. Validation failures, missing resources, rejected origins, expired one-time values and server errors require different handling. A successful request confirms only this processing step; it does not automatically prove that an email was delivered, a payment completed or an identity provider finished an SSO flow. Use anonymised test values for `GET /api/public/access-request/payment-status`. Public examples must not contain real customer data, production-like UUIDs, session JWTs, Widget tokens or concrete historical timestamps. The known platform-wide limit is 2,000 requests per 15 minutes. No separate limit for this individual endpoint is proven, so clients should still cap retries and avoid uncontrolled polling. Idempotency matters when retrying this route. A non-idempotent POST must not be sent again automatically after an ambiguous network interruption, because the original request may already have created a side effect. Logs should record status, error code and a safe request reference, but never passwords, reset tokens or other credentials. This is directly relevant to “GET /api/public/access-request/payment-status”. The source of truth for “GET /api/public/access-request/payment-status — API Reference” is the API registry under `app/frontend/src/content/api-reference/` together with the corresponding backend route and tests. A negative test or a similarity to another code path must not be treated as a complete live verification. This Help Center entry must state precisely whether a claim comes from schema, automated test or safely observed live behaviour.

{"ok":true,"data":{"paypal_ready":false,"mode":"sandbox","paypal_sandbox_ready":false,"stripe_ready":false,"stripe_sepa_enabled":false}}