Skip to main content
Evaluate payment readiness before authorization and optimize payment retries. After your customer has connected their credit cards, evaluate each card before attempting a payment. Method returns behavioral signals used to estimate payment readiness and recommends when to retry failed payments.
Public preview. Preauth Signals is in public preview. Contact your Method CSM to request access.

​
Prerequisites

Before using Preauth Signals, complete the Getting Started flow:
  • Entity created
  • Identity verified
  • Credit cards connected

​
Why Use It?

  • Reduce involuntary churn: Identify the best time to retry failed payments.
  • Increase authorization rates: Know a payment’s likelihood of success before sending it to the network.

​
How It Works

Before attempting a payment, create a Preauth Signals assessment for the card, then retrieve the result to decide whether to authorize now or retry later.
1

Create Preauth Signals

Create a Preauth Signals assessment with POST /preauth. Provide either an authenticated Method account_id or a card object to identify the payment method. You can also include purchase context, such as the transaction amount or merchant category code (MCC), to improve the assessment.
2

Retrieve Preauth Signals

Retrieve the completed assessment with GET /preauth/{preauth_id} to determine whether to authorize the payment immediately or retry later.
Use success_likelihood to choose the best card for a payment, and optimal_retry_date to schedule retries for failed payments.

​
What’s Next

Wallet Intelligence

Retrieve wallet-level insights to personalize customer experiences.

Preauth Signals API Reference

Full API documentation for Preauth Signals.