We’re excited to announce posted
, a new payment status that closes the loop on payments by confirming when they have successfully landed in your users’ accounts.
With real-time account data, Method now provides a level of visibility that was previously unavailable in the U.S. financial system. By knowing if and when a payment has been applied, you can deliver timely and actionable updates to your users—boosting confidence and creating a seamless payment experience.
Key highlights:
2024-04-04
) going forward.We’re excited to introduce Method’s new visual identity, marking a new chapter in our journey under the same thesis we had on day one: consumer financial data is a walled garden, and we’re going to be the ones to open it up.
The updated design features:
Read more about the redesign here.
Webhook Errors now includes detailed explanations of issues that caused your webhook to be disabled.
Webhook objects now feature an error
field following the common Method error format. The error codes for webhook errors are:
WEBHOOK_DISABLED_FAILED_OTHER
: Indicates five consecutive failures not classified as 4XX, 5XX, or timeouts.WEBHOOK_DISABLED_RECEIVED_4XX_ERROR
: The endpoint returned client errors (4XX) five times.WEBHOOK_DISABLED_RECEIVED_5XX_ERROR
: The endpoint returned server errors (5XX) five times.WEBHOOK_DISABLED_TIMEOUT_ON_RESPONSE
: No valid response received within 5 seconds for five consecutive attempts.We’ve expanded our API capabilities by introducing list functionality for the following resources, allowing you to retrieve comprehensive collections, such as all updates or credit scores, for a specific account or entity.
card_brand
in the products
array when creating an Element Token.method-python
).
list
endpoints are now available in the Python client.posted
as an enum value for the payment.status
field.method-node
).
list
endpoints are now available in the Node.js client.posted
as an enum value for the payment.status
field.We’re excited to announce posted
, a new payment status that closes the loop on payments by confirming when they have successfully landed in your users’ accounts.
With real-time account data, Method now provides a level of visibility that was previously unavailable in the U.S. financial system. By knowing if and when a payment has been applied, you can deliver timely and actionable updates to your users—boosting confidence and creating a seamless payment experience.
Key highlights:
2024-04-04
) going forward.We’re excited to introduce Method’s new visual identity, marking a new chapter in our journey under the same thesis we had on day one: consumer financial data is a walled garden, and we’re going to be the ones to open it up.
The updated design features:
Read more about the redesign here.
Webhook Errors now includes detailed explanations of issues that caused your webhook to be disabled.
Webhook objects now feature an error
field following the common Method error format. The error codes for webhook errors are:
WEBHOOK_DISABLED_FAILED_OTHER
: Indicates five consecutive failures not classified as 4XX, 5XX, or timeouts.WEBHOOK_DISABLED_RECEIVED_4XX_ERROR
: The endpoint returned client errors (4XX) five times.WEBHOOK_DISABLED_RECEIVED_5XX_ERROR
: The endpoint returned server errors (5XX) five times.WEBHOOK_DISABLED_TIMEOUT_ON_RESPONSE
: No valid response received within 5 seconds for five consecutive attempts.We’ve expanded our API capabilities by introducing list functionality for the following resources, allowing you to retrieve comprehensive collections, such as all updates or credit scores, for a specific account or entity.
card_brand
in the products
array when creating an Element Token.method-python
).
list
endpoints are now available in the Python client.posted
as an enum value for the payment.status
field.method-node
).
list
endpoints are now available in the Node.js client.posted
as an enum value for the payment.status
field.