Platform-Managed Transaction Limits (Q2 as Source of Truth)

Last updated: June 11, 2026

Summary

PayRecs can be configured to use Q2 Online Banking as the single source of truth for the transaction limits that apply to international payments. When this is enabled for a profile, PayRecs stops keeping its own editable copy of those limits and instead enforces the limits that come from Q2. This removes the drift that used to build up between the two systems and removes the need for an operator to re-enter limits by hand.

This shipped in release 73.0.0 (ENG-1537) and is deployed to production. It requires PayRecs admin setup, described below.

What changed

PayRecs has always pulled limit values from Q2 and has always enforced the Q2 Funds Transfer limits as a ceiling on international payments (these are refreshed when a user logs in via SSO). Separately, PayRecs also kept its own copy of profile-level and user-level international limits, which an operator could edit. Those PayRecs-side values were only seeded from Q2 at onboarding and were not kept in step with Q2 afterward, so the two could drift apart and an operator had to re-enter changes manually.

With this update, a profile can be set to use platform limits. When that is on:

  • PayRecs clears its own stored international limits for the affected profile and its users (they are set to empty/unlimited).

  • The Q2 platform limits become the only limits PayRecs enforces for that profile.

  • The values in effect are whatever is configured in Q2, refreshed on SSO login.

Which Q2 limits govern

  • This is not specific to the International (GT Flavor) payment type. It applies to partners on standard Funds Transfer as well.

  • When a partner has the GT Flavor module engaged, Q2's flavor limits are what flow in. When flavor is not engaged, Q2's standard Funds Transfer limits are what flow in and govern. Either way, PayRecs defers to the limits Q2 reports.

  • If Q2 reports no limit for a given dimension, a PayRecs system-wide hard cap applies as a final backstop (it is not unlimited).

  • Ultimately the transfer is backstopped by the the Q2 mechanism in moving the funds

Advantages

  • Q2 is the single source of truth for the limits PayRecs enforces on the profile. There is no second, separately-edited copy to drift out of date.

  • Limit changes made in Q2 take effect on the user's next SSO login, without an operator re-entering them in PayRecs and without a re-onboarding step.

  • Removes a recurring class of issues where a payment was blocked or allowed based on a stale PayRecs-side limit.

  • Removes the risk of an operator accidentally overwriting a Q2-managed value inside PayRecs, because PayRecs no longer presents those fields for editing.

  • ⭐⭐ Temporary limit changes can be administered from Q2 and don't require a corresponding PayRecs update.

Setup (PayRecs admin)

This is backend configuration handled by a PayRecs admin. There is no self-serve toggle in the partner or sub-company admin UI in this iteration.

  • It is enabled at the partner level (partner.config.platform.usePlatformLimits).

  • It can be overridden on an individual profile (profile.usePlatformLimits). A profile left unset inherits the partner setting.

  • New profiles created under a partner inherit the partner default at creation time.

Before enabling for a bank, note the following:

  • Enabling this clears the affected profile's and users' PayRecs-side international limits. Any limits previously entered manually in PayRecs for those profiles and users are dropped in favor of the Q2 platform limits. The clearing is applied the next time the profile/user is saved or synced (for example on the next SSO sync or a back-office edit), not as an instant bulk wipe. Confirm the bank's Q2 limits are correct before enabling, and communicate the change to the operator.

  • This is one-way. PayRecs reads from Q2 and does not write limits back to Q2.

How this changes the UI

When a profile uses platform limits:

  • Company onboarding / sub-company wizard: the PayRecs limit fields are no longer shown (they are hidden, not shown as locked/read-only).

  • Q2 platform onboarding wizard: the Limits step is replaced with a short note — "Transaction limits for this profile are managed by your platform. There is nothing to configure here."

  • User wizard: the user-level PayRecs limit fields are likewise hidden.

  • Sub-company overview (back office): the Limits card displays the current Q2 platform (Funds Transfer) limits in effect, read-only, instead of PayRecs-side values.

So a partner admin can still see the limits in effect, but cannot edit limits inside PayRecs for these profiles. Limits are changed in Q2 Online Banking.

Things to know

  • The governing limits are the Q2 Funds Transfer limits. This applies whether or not the GT Flavor module is engaged — it is not limited to the International (GT Flavor) transaction type.

  • Sub-companies (subsidiaries) inherit limits from their parent profile and are not configured independently for this setting.

  • To change a limit once this is enabled, update it in Q2 Online Banking. The new value governs after the next SSO sync that picks it up.