Pay Now Link Not Working – Could not find payment processor

Applies To: Work 365 (Dynamics 365 / Power Platform)
Audience: Billing Teams | Finance Teams | System Administrators

Overview

When users click Pay Now on a Work 365 invoice and see:

“Could not find Payment Processor with ID [GUID] in DB. Please ensure the upgrade process is complete.”

…the invoice or its Billing Contract is pointing to a missing, inactive, or wrong Payment Processor—commonly after upgrades, integration changes, or sandbox refreshes.

Key Concepts

• Payment Processor: The configured gateway (e.g., Authorize.Net, Stripe, GoCardless) used by Work 365 for hosted payments.

• Billing Automations → Payment Processor (on Billing Contract): The pointer Work 365 uses when generating Pay Now links.

• Pay Now Link: A URL/token generated on the Invoice that references the selected Payment Processor configuration.

How It Works (at a glance)

1. The Billing Contract stores the default Payment Processor.

2. When Pay Now is generated from an Invoice, Work 365 embeds the processor ID into the hosted-payment link.

3. If that processor record is inactive/deleted or the contract has no processor set, the Pay Now page cannot build the payment form and throws the error.

Symptoms

• “Could not find Payment Processor with ID … in DB” when using Pay Now.

• Pay Now page opens but the hosted payment form never loads.

• Payments worked previously but stopped after an upgrade, integration change, or sandbox migration.

Root Cause

• Invoice or contract references a deactivated/deleted processor.

• Billing Contract → Billing Automations → Payment Processor is blank or points to an inactive record.

• Environment refresh/processor switch left invoices pointing to an outdated processor ID.

Prerequisites

• Ability to edit Invoices and Billing Contracts.

• You know the correct, currently supported processor (Authorize.Net, Stripe, GoCardless, etc.).

Resolution

1) Verify the Payment Processor Is Active

• Navigate: Work 365 → Administration → Payment Processors.

• Open the intended processor and confirm:

  • Status = Active

  • Credentials (API keys/merchant account) are valid

  • Only the intended processor is Default (if you use a default)

2) Fix the Billing Contract Reference

• Open the affected Billing Contract.

• In Billing Automations, set Payment Processor to the correct Active processor.

• Save.

3) Regenerate the Pay Now Link

• Open the affected Invoice.

• From the ribbon: Work 365 → Regenerate Pay Now Link.

• Save the invoice and click Pay Now to test.

Validate the Fix

• Reopen the invoice → Pay Now should load the hosted payment page.

• If the page loads but the charge fails, check processor logs for:

  • Card declines (AVS/CVV/expired)

  • Invalid credentials/API keys

  • Unsupported currency/merchant settings

Prevention & Best Practices

FAQs / Common Questions

Q: Do I need to touch every invoice?
A: No. Fix the processor and Billing Contract, then Regenerate Pay Now Link only for invoices where customers will use Pay Now.

Q: Can I have multiple processors?
A: Yes. Ensure each Billing Contract references the intended active processor.

Q: Why did this start after a sandbox copy?
A: Processor records (and IDs) differ across environments; the copied contract/invoices may point to IDs that don’t exist in the target.

Additional Resources

• Work 365 Documentation – Payment Processor Configuration

• Work 365 Support Portal – Billing Contract Automation & Payment Processor Setup

Summary

This error indicates the Pay Now link is referencing a missing or inactive Payment Processor.
Fix: Activate the correct processor → update the Billing Contract → Payment Processor → Regenerate Pay Now Link.
Once corrected, Pay Now will load and process payments as expected.