Method Expands Developer and Compliance Features Across Fintech Infrastructure

According to a recent LinkedIn post from Method, the company’s February changelog emphasizes expanded capabilities across its fintech infrastructure platform. The post highlights enhancements to Forwarding Requests, Connect, Payments, Payment Instruments, Webhooks, and API documentation, with a focus on compliance, testing, and user consent flows.

The post suggests that Method is extending its Forwarding Requests feature to support identity data via Entity Bindings, enabling KYC handoffs and card tokenization without exposing raw PII. It also describes new Credit Score Simulations that allow developers to trigger synthetic credit score changes in a development environment to validate alerts, eligibility rules, and pricing logic.

As shared in the post, Method is introducing a new webhook event, entity.new_accounts_pending_consent, designed to detect new accounts for users who have not opted into automatic consent. This mechanism appears intended to support more granular user consent management and could help clients address evolving regulatory expectations around data access and authorization.

The update also mentions refinements to Connect, including the ability to filter by product so that end users only see accounts relevant to a particular offering. For investors, these incremental product improvements may strengthen Method’s value proposition to financial institutions and fintech developers, potentially increasing integration stickiness and supporting higher long-term transaction and usage volumes.

From an industry perspective, the emphasis on PII minimization, consent workflows, and robust sandbox testing aligns with rising regulatory and risk-management requirements in embedded finance. If these features are adopted widely, Method could improve its competitive positioning within the account connectivity and payments orchestration space, though the post does not provide metrics on customer uptake or revenue impact.