HomeGuidesRecipesAPI ReferenceChangelog
Log In
Changelog
These docs are for v2.2.8. Click to read the latest docs for v2.3.5.

SANDBOX - v2.3.5 - 2025-02-05

This Sandbox release focuses on improving USD on-ramps via ACH Pulls (Plaid), expanding remittance support, strengthening webhook security, and continuing behind-the-scenes work on fraud detection and reporting.


✨ What’s New

  • 🇺🇸 Improved USD on-ramps via ACH Pull (Plaid)
    • No manual bank details
    • Secure Plaid-based bank linking
    • Support for multiple linked bank accounts (with clear limits)
  • 🇻🇳 Vietnamese Dong (VND) added for remittance payouts
  • 🔐 Webhook URLs now require HTTPS only
  • 📬 Clearer webhook documentation for linked bank account status changes
  • 🧾 Stronger REST API validation for KYC applicant data

🇺🇸 USD On-Ramps via ACH Pull (Plaid)

We’ve improved the ACH Pull flow to make USD on-ramps simpler, more secure, and easier to integrate.

What’s Improved

  • Users no longer manually enter bank account details
  • Bank accounts are linked securely using Plaid
  • Users can link up to two bank accounts to their profile
  • Each ACH pull explicitly references the selected linked bank account
  • Webhooks provide clear visibility into bank account readiness

This creates a more consistent onboarding experience and reduces failed pulls caused by invalid or incomplete bank data.


⚠️ Important Limitation: Bank Linking & ACH Pull Limits

To ensure predictable behavior and a consistent user experience, the ACH Pull flow enforces clear limits.

Current limits (per user):

  • Maximum 2 linked bank accounts at any time
  • Maximum 1 bank linking action per 24 hours
  • ACH pulls are only possible from already-linked accounts

Because of these limits, linking multiple bank accounts and switching between them within the same day is not supported and may result in errors.

Example Scenario

  1. User links Bank Account A → allowed
  2. User attempts to link Bank Account B on the same day → ❌ blocked (linking limit reached)
  3. User initiates ACH pulls from Account A → works as expected
  4. User must wait 24 hours before linking another bank account

This behavior is intentional and helps avoid confusing edge cases where ACH pulls may fail depending on previous actions.

Recommended Merchant Guidance

To provide a smoother user experience, we recommend:

  • Encouraging users to link one bank account at a time
  • Treating bank linking as a deliberate, infrequent action
  • Clearly communicating that ACH pulls work reliably once an account is linked
  • Avoiding UX flows that promote frequent switching between bank accounts

We’re actively reviewing these constraints and working on improvements to make multi-account usage more flexible in future releases.


🧾 API Validation & Documentation Updates (REST API)

We’ve strengthened validation and documentation for KYC applicant creation to improve data quality and reduce downstream verification issues.

KYC Applicant Creation
Endpoint: POST /user/kyc/applicant

What changed:

  • address_line_2 is now validated using a stricter character pattern
  • state is now validated according to country-specific rules

What this means:

  • Loosely formatted or invalid address data may now be rejected
  • Merchants should ensure applicant address fields comply with the updated validation rules

🌐 Webhook URLs Now Require HTTPS

To improve security, all webhook-related URLs must now use HTTPS.

Affected fields:

  • webhook
  • plaid_redirect_url

❌ No longer allowed:
http://api.example.com/webhooks

✅ Required:
https://api.example.com/webhooks

Action required:
Please update your webhook configuration to ensure all URLs use HTTPS.


🌍 Currency Expansion: VND Support

Remittance payouts are now supported in Vietnamese Dong (VND).

Use case:
Enable remittance flows to Vietnam with full beneficiary support.


🔐 Ongoing Fraud & Compliance Improvements

We’re continuing internal work to improve fraud detection, monitoring, and reporting capabilities. These changes are mostly behind the scenes for now, but they lay the foundation for stronger merchant controls and better visibility in upcoming releases.


🔮 What’s Next

Here’s what we’re actively working on:

  1. Third-Party On-Ramp Controls
    Merchants will be able to disable third-party onramps if they choose, giving more control over how users fund their accounts.

  2. Upcoming Currency Support

    • 🇨🇴 Colombian Peso (COP)
    • 🇯🇵 Japanese Yen (JPY)

More details coming soon as these features approach release.


🙌 Thanks for Building with Us!

This Sandbox update focuses on smoother USD on-ramps, clearer operational limits, expanded remittance support, and stronger security defaults — while preparing the platform for deeper compliance and fraud tooling.

If you have questions or want help testing these flows, feel free to reach out! 💬