At release time, OpenEnvoy confirms the invoice is still valid, the supplier is approved, required approvals are complete, and exceptions are resolved.
Payments go out as a batch you review and approve. The person who builds the batch is a different person from the one who approves it. Rules by amount, payment type, vendor, or entity add approvers where you want them.
Card, ACH, or wire, set per vendor. Virtual cards are single-use, issued for the approved invoice total, and delivered securely to your vendor by email. Cancel, freeze, or reissue a card without disrupting other batch payments.
A first run can be entirely ACH and wire. Card applies per vendor, by rules you set, and you can change it at any time. Vendors that charge card fees stay on ACH or wire. Your ERP remains the source for what you pay; OpenEnvoy verifies and executes.
Each virtual card is single-use and issued for the approved invoice total, so the payment matches the number your team verified. For card vendors there are no banking details to hold or maintain. A card can be frozen, cancelled, or reissued without disturbing the rest of the run. Your vendor sees when the card was sent, and you see when it was viewed and charged.
Vendors receive a secure email with the payment and remittance. Your vendors are charged nothing to receive a virtual card payment. You choose when and how they hear about it, and OpenEnvoy provides the sender identity and remittance detail so nothing arrives as a surprise.
Your approval workflows and vendor master stay where they are. Verified Payments works on top of your ERP.
Tokens cover document processing. Payment execution is priced separately. On Essentials your rate is shown at signup with a consumption tracker. On Scale and Enterprise it is on your order form. Available to US customers.
Verified Payments confirms you're ready to pay before money moves. At release time, OpenEnvoy confirms that the invoice is still valid, the supplier is approved, required approvals are complete, and exceptions are resolved. Then the run executes, as a controlled batch with rollups and an invoice-level audit trail. Virtual card, ACH, and wire are methods inside that same run. You choose the method per vendor or per invoice; the verification and the audit trail are identical either way. Verified Payments works on top of your ERP, not instead of it. Available in the United States.
Verified Payments runs ACH, wire, and virtual card through the same verified batch, with the same approvals, the same controls, and the same audit trail. You can run entirely on ACH and wire. Where a vendor accepts card, each card is single-use and issued for the approved invoice total, so the payment matches the amount you verified.
You pay them the way you pay them today. Card applies per vendor, by rules you set, and where that vendor accepts it. The rest of your payment run is unaffected.
You set the method by vendor or by rule, and you can change it at any time. Verification, approvals, and the audit trail are identical across the three, so the method is an operational choice. Card is the strongest option where a vendor accepts it: a single-use card issued for the invoice total holds the payment to the verified amount and can be frozen or reissued without disturbing the rest of the run. For card vendors, you also don't hold or maintain banking details.
Payment execution is priced separately from tokens and shown at signup (Essentials) or on your order form (Scale and Enterprise). Your vendors are charged nothing to receive a virtual card payment.
To US customers today. Document capture and Ask OE support international entities in the meantime.
QuickBooks, Sage Intacct, NetSuite, Dynamics 365, SAP, Oracle, Workday, and JDE, with SFTP where needed.
Verified Payments Visa® Commercial cards are powered by Stripe and issued by Celtic Bank.
Stripe Issuing balances are provided in the US by Stripe Payments Company, licensed money transmitter, with funds held at Stripe's bank partners, Members FDIC.
