Skip to main content
Following these practices helps ensure your integration remains stable, secure, and operationally resilient as your disbursement program scales.

​
Request Management

Ingo Payments enforces rate limits to protect platform stability for all clients. Limit your integration to no more than five simultaneous requests per second to avoid triggering rate-limiting controls. If your program requires higher throughput — for example, during batch processing or high-volume disbursement windows — contact Ingo’s Partner Technical Support before you hit the limit. Your team can work with you to evaluate your volume needs and configure appropriate accommodations.

​
Fraud Controls

Outbound payment programs create a direct cash-out channel that attracts fraud. Implementing layered controls — both internal to your organization and external through your banking and vendor relationships — significantly reduces exposure. Internal controls should include approval workflows, segregation of duties, and transaction monitoring. External controls — such as Ingo’s risk verification services and your banking partner’s transaction alerts — provide an independent validation layer. Together they ensure that breakdowns in one layer don’t create undetected exposure. Key principles for outbound payment fraud control: Maintain strict segregation of duties so no single employee can both initiate and approve a payment. Establish a reconciliation cadence that identifies discrepancies before they compound. Review recipient verification configurations regularly to ensure your risk tolerance matches current fraud patterns. Treat payment failures and unusual return rates as fraud signals and investigate promptly.

​
Prefunding

If your program is funded exclusively via ACH or wire transfer, maintain a 3–5× projected volume buffer in your prefund account at all times. ACH and wire rails are subject to bank cutoffs, non-business days, and settlement delays — without a buffer, funding gaps can interrupt disbursements. Plan your funding schedule around the rolling 15 and 30-day velocity limits configured for your program. Monitor your prefund balance and initiate replenishment well before the buffer is depleted — same-day wires and next-day ACH are not always feasible or timely options.

​
Communication Management

Maintain a distribution list for Ingo operational communications rather than routing them to a single contact. Maintenance schedules, outage notifications, and reconciliation alerts need to reach the right people across operations, finance, and technology simultaneously. Review and update your distribution list whenever key personnel change. Establish internal escalation paths so your team knows who to contact and what actions to take when critical communications arrive.

​
Statement Descriptors

Statement descriptors appear on cardholders’ and bank account holders’ transaction records. A clear descriptor reduces customer inquiries, disputes, and chargebacks. Limit your descriptor to 10–13 characters — longer values may be truncated by networks or issuers. Include a reference to your company name so recipients can immediately identify the transaction source. Card networks and issuers may override your configured descriptor at their discretion; this is outside Ingo’s control. Work with your Integration Manager to configure descriptors by transaction type during onboarding.