Why This envelope does not request a payment is not a payment-not-live state

Collect a payment on send stores amount, currency, and a description on that envelope. A signer POST to /api/sign/:token/pay on an envelope that never collected returns This envelope does not request a payment. Charged stays false. Live stays false. That is no-pay honesty: pay has nothing to collect, Payments not live is a different state on an envelope that did request, and opening Billing will not “attach a card request after send.”

Why a requested payment still does not charge is payments honesty. Why workspace checkout is not open is billing checkout honesty. Desk help is Docs. This guide is why pay names an envelope that never collected, and why that name is not the Payments-not-live state.

The FAQ and payments on Features start from Collect a payment on send. Ask Inkpacket for why This envelope does not request a payment is not a payment-not-live state to open this article. Ask how payments work to open help. Those phrases stay on the product screens. This article is the public version of This envelope does not request a payment — the string the pay route already uses next to an envelope with paymentEnabled off.

What no-pay covers

• Signer pay on an envelope that never collected. This envelope does not request a payment.
• The same POST after send without collectPayment. paymentEnabled stays off. The same 400.
• Signer pay on an envelope that did collect, without Stripe keys. Payments not live / not configured. That is the not-configured state, not this 400.
• Send with collectPayment and no positive amount. Collecting a payment requires a positive amount. That is the send-form door, not this pay route.

Reading This envelope does not request a payment is not a send. The original send already counted if the envelope left draft. Free allows 5 packets a month. A refused pay does not return HTTP 402 ENVELOPE_LIMIT. Payments not live is a collected request whose Stripe keys are missing. Payment currency must be a 3-letter code and Payment description must be 160 characters or fewer are send-form format doors. Those strings are other doors. An envelope that never collected is this door.

What this is not

• Not Payments not live / not configured. That string is a collected request whose keys are missing.
• Not Collecting a payment requires a positive amount. That string is send with collectPayment and no cents.
• Not workspace checkout. Billing is not open. Paying a listed plan does not attach an envelope payment.
• Not a charge. This pass never opens live Checkout. No-pay is the missing request, not a successful card.

If the work needs a payment line, send a new envelope and turn on Collect a payment before send. Do not POST pay on the first id hoping Billing will attach an amount. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails on that new send. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live — that flag appears after collect, not instead of this 400. None of those flags hide This envelope does not request a payment or count a refused pay toward the monthly cap.

The click-path

1. On send, turn on Collect a payment and set a positive amount. Then send.
2. If pay returns This envelope does not request a payment, this envelope never collected. Do not open Billing to attach an amount after send.
3. If pay returns Payments not live / not configured, you did collect. That is the not-configured state. The signer was not charged.
4. If send of a new envelope returns HTTP 402 ENVELOPE_LIMIT, that is the monthly cap, not this pay 400.
5. On a phone, Documents is a drawer row. Payments is a send-form hash after upload. Help is not a drawer row — it stays in the header.

Hash-before-file on Documents → new #payments is why Upload a PDF first is not a rejected upload. Workspace prices stay published, not charging — Free vs paid lanes. Ask Inkpacket for why This envelope does not request a payment is not a payment-not-live state to open this article. Ask how payments work to open help. Ask collect a payment to open the send form.

Ask and the missing request

Ask Inkpacket for why This envelope does not request a payment is not a payment-not-live state to open this article. Ask how payments work to open help. Marketing Ask stays site Q&A and deep links. It will not attach a payment after send, charge a card, or increment the monthly cap from this article. Collect on send. Pay is the other door only after that checkbox.

Caps and what is not open yet

Reading This envelope does not request a payment is not a send. Send of a draft that later collects is. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not attach a payment after send or hide the no-pay string. The FAQ and FAQ use This envelope does not request a payment in the same words.

Collect on send. Then the pay route has something to record. Open a workspace on Free — see published pricing — and POST pay on a throwaway envelope that never collected so no-pay honesty is a named 400 you already read, not a checkout you opened to “attach a card request” this pass does not ship.