If you’re tired of chasing down signatures and payments from business clients, you’re not alone. Collecting money can get messy, especially with B2B deals where paperwork and payment often get tangled up. Here’s the good news: you can use Docusign payment integrations to get contracts signed and paid in one shot. This guide breaks down exactly how to set it up, what works well (and what doesn’t), and some honest advice from the trenches.
Who’s this for? Anyone in B2B sales, finance, or operations who wants to stop cobbling together contracts, invoices, and payment links. If you use Docusign or are considering it, you’ll get the most out of this.
Why Collect Payments with Docusign?
Let’s get real: most B2B payment “automation” is just a fancy way of sending your customer a PDF to sign and a link to pay somewhere else. This slows things down and gives everyone another excuse to delay. Docusign’s payment integrations let you:
- Combine signing and payment in one workflow
- Reduce back-and-forth with customers
- Help your finance team track who actually paid (not just who signed)
- Get money in the bank faster
But—full honesty—Docusign is not magic. There are limitations, and it’s not always a drop-in replacement for your accounting system. Still, for a lot of use cases, it’s a big step up from chasing emails and hoping for the best.
Step 1: Know What Docusign Payments Can (and Can’t) Do
Before you get excited, let’s set expectations. Docusign Payments is basically an add-on that lets you request payment at the same time as a signature. It integrates with payment processors like Stripe, PayPal, Authorize.Net, and some others. Here’s what you need to know:
What Works:
- You can request payment as a required step during signing.
- Supported payment types: credit cards, ACH/bank transfer (depends on your processor).
- Works well for one-off transactions: contracts, service agreements, onboarding fees, etc.
- Payment confirmation is tied to the envelope (the document workflow), so you know who paid and when.
What Doesn’t:
- No built-in recurring billing or subscriptions (you’ll need your payment processor for that).
- Not a replacement for full-blown invoicing or accounting tools.
- Integrations are only as good as the processor you choose (Stripe is the most flexible, others may have limitations).
- You’ll need a Docusign Business Pro or Enterprise plan.
Pro tip: If your B2B deals are complex, or you need custom invoices, it’s better to use Docusign payments for deposit or contract fees, and handle the rest through your usual accounting system.
Step 2: Set Up Your Payment Processor
You need an account with a supported payment processor. Stripe is the most popular choice (and the easiest to set up), but Docusign also works with PayPal, Authorize.Net, and a few others. Here’s how to get rolling:
- Sign up for Stripe (or your processor of choice).
- Go to Stripe and create a business account.
- Verify your business and banking details.
- Make sure you have the right Docusign plan.
- Payments require Business Pro or above. If you’re on a lower tier, you’ll need to upgrade.
- Connect your payment processor to Docusign.
- Log in to Docusign.
- Go to Settings > Integrations > Payments.
- Follow the prompts to connect your Stripe (or other) account.
Heads up: Test with a small transaction first. Payment integrations can get weird with currency, banking, or region restrictions.
Step 3: Build Your Payment-Enabled Envelope Template
Now you need a Docusign template that collects both signatures and payments. Here’s how to set it up:
- Create a new template.
- Go to Templates > New Template.
- Upload your contract/agreement document.
- Add recipient roles.
- Typical B2B: you (sender), client (signer/payer).
- Add signature fields as usual.
- Add a payment field.
- In the Fields section, drag the Payment field onto the document where you want the payer to enter payment info.
- Configure the payment amount (fixed or editable).
- Set your payment processor (should appear if you connected Stripe/PayPal already).
- Optional: Add line items, tax, or allow your client to enter an amount (e.g., for deposits).
- Save the template.
What to ignore: Don’t try to hack in recurring payments or complex payment logic with Docusign templates. It’s not built for that. Keep it simple.
Step 4: Send a Payment-Enabled Envelope
With your template ready, you can send out a payment-enabled envelope to your customer. The steps:
- Start a new envelope using your template.
- Add your recipient’s info.
- Customize the message (optional). This is a good place to set clear expectations: “Please sign and pay to get started. Payment must be completed to finalize your agreement.”
- Send.
Your customer will receive a link. They’ll go through the usual Docusign signing steps, and when they hit the payment field, they’ll be prompted to enter their card or bank info. Payment is processed immediately, and the contract is only “completed” when payment goes through.
Step 5: Track Payments and Follow Up
After sending, you can monitor the status of your envelopes:
- Completed: Signer has signed and paid.
- Waiting for Payment: Customer signed but didn’t pay (rare, but possible if you set it up that way).
- Declined/Voided: Something went wrong, or customer bailed.
You’ll get notifications, and payment receipts are available in your payment processor dashboard (e.g., Stripe). Docusign will show payment status in the envelope history, but for actual accounting, you still need to reconcile in your main finance system.
Pro tip: Don’t rely on Docusign alone for bookkeeping. Use the payment processor’s exports or integrations to sync with QuickBooks, Xero, or whatever you use.
Step 6: Handle Common Issues
Let’s not sugarcoat it—things can go sideways. Here’s what to watch for:
- Payment fails: Card declined, bank block, etc. You’ll get an error. Follow up with your customer or let them try again.
- Signer skips payment: If you make payment optional, someone might “forget.” Always set payment as required unless you have a good reason not to.
- Multiple signers?: Only one can be the payer per envelope. If you need several signatures and a payment, make it clear who’s responsible.
- International payments: Stripe and PayPal support global cards, but fees and currency exchange can get ugly. Check before sending to overseas clients.
- Refunds: You have to handle refunds through your payment processor, not Docusign. There’s no “undo” button for a payment in Docusign.
Step 7: (Optional) Automate Further with Integrations
If you want to get fancy, you can connect Docusign to your CRM, ERP, or billing tool. Options:
- Zapier: Good for simple “when envelope is completed, do X” workflows.
- Native integrations: Salesforce, NetSuite, and others have built-in Docusign connectors.
- API: If you’ve got developers, Docusign has a robust API. Just know this gets complicated, and you’ll need dev resources.
For most B2B teams, you’ll get 80% of the benefit just using the built-in payments features. Only go deeper if you really need to.
What Actually Works Best (and What to Avoid)
Works Well For:
- Onboarding fees, deposits, setup charges
- Project-based work (get paid before you start)
- Service contracts with one-time or annual fees
- Small-to-midsize B2B deals
Avoid If:
- You need complex invoicing, milestones, or split payments
- Recurring billing or subscriptions are required
- You want deep accounting integration (use your ERP/invoicing tool)
Bottom line: Use Docusign payments to cut friction on deals where a single payment and signature are all you need. For everything else, pair it with your usual financial tools.
Wrapping Up
Collecting payments through Docusign can save you time and headaches, but don’t overthink it. Set up your payment processor, build a simple template, and test it with a real customer. Start small. Tweak as you go. The easiest setup is usually the best—don’t let “perfect” slow you down.