Ingo Payments · Notify — Managed Parties
One call. Every step managed.
Single and multi-party. Fully orchestrated from notification through approval and delivery.
SMS delivery options — Notify can send recipient notifications via SMS through Ingo-managed delivery or through your own SMS infrastructure. With Ingo-managed SMS, Ingo sends directly to recipients and manages consent collection — though notifications identify Ingo as the sender rather than your brand. Many clients integrate their own SMS platform for full brand control, directing recipients to the Ingo-hosted disbursement URL. Both approaches are supported. See Custom Domain & DNS Setup for details, or ask your Integration Manager which approach fits your program.
Capabilities
Multi-Party Orchestration
Define up to three party roles per transaction. Recipients receive and claim
funds. Approvers actively gate the disbursement — funds do not release until
all designated approvers have acted. Interested Parties receive visibility
into the transaction without taking any action.
Coming Soon
Role Delegation — Approvers will be able to delegate their approval authority to another party at any point in the lifecycle. Tell us this matters to your program →
Single-Recipient Disbursements
Every capability available in a single-recipient flow is fully supported.
Notification, identity and OFAC screening, client-configured payment options
with amount-based thresholds, account tokenization, and real-time webhook
updates at every status change — all managed by Ingo from a single staged
notification.
Recipient Enrollment
In Development
Collect payment preferences independently of any disbursement. The fully hosted
enrollment experience will present your configured payment options through the
Embedded Account Capture interface — no portal or payment UI to build or host.
On completion, Ingo returns a customer_account_token ready for use
in any future disbursement. Tell us this matters to your program →Recurring Disbursements
In Development
Decouple enrollment from payment for programs that disburse on a recurring
cadence. Enroll a recipient once; stage subsequent disbursements against their
token without re-collecting account details or re-running the hosted experience.
Ideal for payroll, earned wage access, insurance premiums, and recurring financial
programs. Tell us this matters to your program →API Reference
Notify — Managed Parties exposes one staging endpoint. Cancellation of a staged notification before the recipient has claimed uses the shared Notify Cancel endpoint.Notify — Stage
Submit a notification with recipient details, party roles, disbursement intent,
and notification type. Ingo immediately begins the managed lifecycle on your behalf.
Notify — Cancel
Cancel a staged notification before the recipient has claimed their disbursement.
Managed Parties shares the Cancel endpoint with Notify — Classic.