2025.10.30
What’s new
No new features were released in this update.Why it matters
We’ve made backend improvements to ensure data integrity and consistency across V3 listing endpoints, especially when handling relational data like linked bank accounts.Highlights
- Fixed binding issues between collection objects and resource transformers
- Ensured relational data (e.g., bank accounts) is preserved during transformation
- Added safeguards to prevent data loss during response transformation
2025.10.28
What’s new
We’ve made several enhancements to the V3 API, including unified bank account data across key endpoints and a new onboarding flow for adding bank accounts to persons.Why it matters
These updates give you greater visibility into linked bank accounts, improve onboarding flexibility, and enable support for additional payment rails like FedNow. You can now onboard and validate accounts via Plaid or manually—all with consistent structure and improved intelligence.Highlights
- Unified Bank Account Objects: Bank account details are now included in all V3 listing and detail API responses for People, Merchants, and Businesses.
- New V3 Bank Account Onboarding Endpoint: New v3 API endpoint for adding bank accounts with account intelligence of various versions. This includes:
- Support for both Plaid-based and manual bank account onboarding
- Comprehensive account validation including account holder name verification
- Duplicate detection for manual accounts
- Cleaner Timestamp Responses: Removed unused updated_at fields for a more streamlined response format.
2025.10.22
What’s new:
We’ve added a new status field to all Person-related V3 API responses, including List, Fetch, Onboard, and Update, as well as the PersonCreated and PersonUpdated webhook event payloads.Why it matters:
You can now immediately see the current status of any user in your system. This makes it easier to confirm that a person is in a valid state to transact before initiating a transfer, helping reduce failed attempts and streamline your integration logic.Highlights:
- New status parameter added to V3 API responses for People (List, Fetch, Onboard, Update)
- Included in webhook payloads for both person creation and updates
- Improves visibility into user state and transactional readiness across the platform
2025.10.15
What’s new:
We’ve added a newkyb_rejected_reason field to both the Merchant Create and Merchant Update API responses, as
well as the corresponding MerchantCreated and MerchantUpdated webhook event payloads.Why it matters:
You can now see the specific reason a merchant’s KYB (Know Your Business) verification failed. This provides greater transparency and helps streamline your onboarding and support workflows.Highlights:
- New
kyb_rejected_reasonparameter added to API responses ( Onboard, Update, List, Fetch ) - Included in webhook payloads for both merchant creation and updates
- Ensures consistent, actionable KYB feedback across the API and webhooks
2025.10.10
Maintenance Items
- OpenAPI Documentation Updates: Fixed an issue with the Webhook Registration OpenAPI documentation to specify
that the
webhook_urlfield should be passed as an array to allow for multiple webhook URLs.
2025.10.7
Release Features
- Optimized Business & Merchant Response Payloads:
- Responses: Removed full Person objects from create and update responses
- Relations Object: Responses now include a clean relations object containing only the Person UUID
- OpenAPI Documentation Updates: Updated OpenAPI documentation for Business and Merchant onboarding and update endpoints to reflect the new relational data structure.
Maintenance Items
- Vendor Object in Relations: Resolved an issue where the vendor object was incorrectly appearing in List Person and List Merchant API responses. The relations attribute now correctly returns only allowed UUID references, ensuring consistency across all V3 endpoints.
2025.10.6
Release Features
- V3 API Response Standardization: All V3 APIs of List and Showing (Person, Business, and Merchant) now follow a unified response contract with consistent structure. Error responses are now standardized across all endpoints, providing clearer, more consumer-friendly messages with proper attribute naming in validation errors.
- Enhanced Relational Data: We’ve introduced a new relations object across all V3 endpoints, making it easier to
understand entity relationships:
- Person responses now include related Business or Merchant UUIDs.
- Business responses include the associated Person UUID.
- Merchant responses include the associated Person UUID.
- Webhook Enhancements: Updated Person and Merchant webhook responses to include the new relations object structure, providing cleaner, more relevant information for integrations.
Maintenance Items
- Billing Improvements: Fixed filter inconsistencies in Billing Item and Summary endpoints, ensuring accurate and reliable query results across both endpoints with consistent behavior.