Skip to main content

​
New Features

​
Raw Credit Report Artifacts and Files API

Teams with raw credit report access can now request the bureau report underlying a Connect as downloadable JSON or PDF artifacts. This gives lenders the full bureau file behind a Connect, so underwriting, risk, and compliance logic can run against the same source data Method used. Pass bureau and artifacts when creating a Connect. Equifax and TransUnion are supported:
The completed Connect returns each artifact in its files array. The new Files API provides two ways to access them:
  • GET /files/{file_id} returns File metadata and a temporary download URL
  • GET /files/{file_id}/download streams the original file directly
Files remain available after the Connect completes, allowing lenders to run their existing underwriting and risk logic on the same raw credit report output without maintaining a separate bureau integration. Raw credit report access is enabled per team; contact your Method CSM to get started. For implementation details, visit the Raw Credit Reports guide and Files API documentation.

​
Estimated Statement Attribute

Account Attributes can now return the upcoming payment due date and minimum amount due for supported accounts through the new statement bundle:
  • next_payment_due_date: the upcoming payment due date
  • next_payment_minimum_amount: the upcoming minimum amount due, in cents
Previously this required maintaining an Update subscription and waiting for a refreshed Update to land, and between statement cycles the values were frequently missing altogether. Teams can now schedule autopay and reminders against a real due date, size a payment that reliably clears the minimum, and sequence payments across a user’s accounts by what comes due first. When current statement data is unavailable, Method estimates both values from account history and identifies them with metadata.estimated: true. When a value cannot be determined, the attribute returns an ACCOUNT_ATTRIBUTE_INSUFFICIENT_DATA error rather than a fabricated fallback.
For more information, visit the Account Attributes API documentation.

​
Estimated Credit Card APR

Account Attributes can now return a single estimated_apr for supported credit card accounts with qualifying account history. Card issuers rarely expose an account-level APR through any programmatic channel, which has left teams either asking the end user for their rate or assuming one. Estimated APR lets teams size interest savings, rank refinance and balance transfer offers, and prioritize outreach to the highest-rate balances in a user’s profile, without asking the end user for anything. Every value is identified with metadata.estimated: true and carries a metadata.confidence of medium or high based on the depth of available history, so teams can set their own threshold for acting on it. When an APR cannot be inferred with sufficient confidence, the attribute returns an ACCOUNT_ATTRIBUTE_INSUFFICIENT_DATA error rather than a fabricated fallback.
For more information, visit the Account Attributes API documentation.

​
Changes

​
Payment Processing Windows

Payment processing windows have been updated. Payments using the Method Debit Model are now processed at 1:30 PM CT, and payments using the Prefunded Model are now processed at 3:30 PM CT. Payments submitted before the applicable cutoff are processed same-day; payments submitted after are queued for next-business-day processing. For more information, visit the Payments API documentation.

​
Improvements

​
Idempotency and Stuck-Request Recovery

Improvements to Method’s idempotency system eliminated persistent INTERNAL_BAD_STATE errors on retried requests. Dropped connections now recover automatically on retry, previously stuck requests self-heal rather than remaining locked, and orphaned in-flight requests are released after a short interval. End users no longer become locked mid-flow after a dropped connection. Requests already stuck in INTERNAL_BAD_STATE also recover automatically the next time the end user retries, and no integration changes are required. For more information, visit the API Idempotency documentation. The Method Dashboard now includes:
  • A responsive, collapsible sidebar with improved mobile support
  • Faster global search with a more compact results experience
  • Faster switching between development and production environments
  • Persistence of the most recently used environment across sessions
  • FIS trace IDs on sent and posted payments in the payments view
Users with the Developer role can also create API keys and webhook registrations directly from the Dashboard, consistent with their existing permissions. Together these reduce the time spent locating a request, entity, or payment when responding to a customer question.

​
Payability Check at Account Creation

Method now runs a payability check when an account is created, so teams learn whether an account can be paid at the point of creation rather than discovering it at payment time. This prevents users from attempting a payment that was never going to succeed.

​
Webhook Reliability

Outbound webhook delivery now includes stronger duplicate-delivery protection and prevents queued deliveries from being sent to disabled webhook registrations. Delivery and replay handling have also been hardened to reduce the risk of events being lost during transient service failures. This means fewer events to deduplicate on your side and less reconciliation work after a transient failure, with no change to how you consume webhooks. For more information, visit the Webhooks API documentation.

​
Development Environment

Manual Connect flows can now be configured dynamically, and payments can be simulated against payment instruments without production dependencies. Teams can therefore test a full Connect-to-payment path, including failure cases, before touching a live account. For more information, visit the Development Environment documentation.