{"id":"219141d9-b780-4b8c-b9a4-e1d3c236f788","task":"Collect a payment from a signer during the DocuSign signing ceremony using the Payments feature","domain":"developers.docusign.com","steps":["Configure at least one payment gateway (e.g., a supported processor like Stripe or Braintree) for the account in advance via DocuSign's payment gateway management settings — this account-level setup yields a gatewayAccountId to reference and is a prerequisite before any API call can charge a signer.","When building the envelope's recipient tabs, add a Formula tab configured with a paymentDetails object (rather than a plain signature/text tab); paymentDetails includes gatewayAccountId, gatewayName, currencyCode, and a lineItems array (each with name, description, amount/quantity) describing what's being charged.","Send the envelope as normal; during the signing ceremony, DocuSign inserts a payment collection form (e.g., credit card entry) at the payment tab's location before the signer can finish signing.","DocuSign passes envelope ID, recipient name/email, and the configured line-item details to the gateway to process the charge; DocuSign does not store or process the raw card data itself.","After completion, check the paymentDetails status/chargeId fields on the completed envelope to confirm the charge succeeded, and reconcile against the gateway's own transaction records.","Plan workflow and retry/void logic around payment being a blocking step: if the signer cannot complete payment, the envelope cannot be completed."],"gotchas":["Payments requires a supported gateway to already be connected and configured at the account level — there is no DocuSign-native payment processor; the API call is meaningless without that setup, which is typically done through the DocuSign web console.","The payment 'tab' is implemented as a Formula tab carrying a paymentDetails payload, not a dedicated top-level tab type — teams often mistakenly look for a nonexistent PaymentTab object.","DocuSign explicitly does not store cardholder data — for durable reconciliation you must capture the gateway's own chargeId rather than expecting DocuSign to be the system of record for payment details."],"contributor":"waymark-seed","created":"2026-07-09T18:42:26.286Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/219141d9-b780-4b8c-b9a4-e1d3c236f788"}