Where a payment stands (EAS-119)
Polled by the signer's page after the card is confirmed. When Stripe's webhook has not landed yet and the payment is still open, the PaymentIntent is read from Stripe, so a signer who has just paid is never left waiting on webhook delivery.
View as MarkdownPath Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/public/signing/string/fields/string/payment"{ "payment": { "status": "requires_payment", "paid": true, "amountMinor": 0, "currency": "string", "description": "string", "failureMessage": "string", "failureCode": "string" }}Start, or resume, the payment for a payment field (EAS-119)
Idempotent: a double click, a reload, or a retry after a declined card all land on the same PaymentIntent. The amount and currency are the field's own, snapshotted when the payment starts — nothing in the request can change them. Requires the same signing state as signingComplete (pending, before the deadline, this signer's turn, not yet signed or declined), and the field must be a payment field assigned to the caller. The response carries the client secret that Stripe.js confirms in the browser; whether the payment succeeded is never reported by the browser — it is learned from Stripe's webhook, or by reading the PaymentIntent server-side.
Whether this workspace can take payments (EAS-119)
The workspace's Stripe Connect state. A workspace connects its own Standard Stripe account, and payments are charged directly on it, so the money goes to the workspace and not through Easerix. Pass refresh=1 to read the account back from Stripe first, which is how the settings page picks up a finished onboarding without waiting for a webhook. A document with a payment field can be sent only when chargesEnabled.