search
Explore with DeepWikiJoin Slack CommunityContact Us

hand-holding-circle-dollarPayment Method (Card)

Hyperswitch provides flexible payment processing with multiple flow patterns to accommodate different business needs. The system supports one-time payments, saved payment methods, and recurring billing through a comprehensive API design.

circle-info

hashtag
Integration Path

hashtag
Server-to-Server (S2S) Payments

Refer to this section if you intend to use the SDK exclusively for vaulting/storing card details. In this scenario, the actual payment execution is handled via S2S API calls from your backend to Hyperswitch, offering you more granular control over the transaction lifecycle.

Payment method flows leverages all the capabilities available in Paymentsarrow-up-right. The primary goal here is to allow the business to control the payment journey via S2S APIs and a token or payment_method_id

The business can use the Payment Method SDK or /payment-methods API to first capture the card details and create a payment_method_id

The business can then use the payment_method_id in /payments API to perform all functionalities supported by the Paymentsarrow-up-right flow.

Payment Method Lifecycle

The Payment Method flow leverages the full suite of Hyperswitch Paymentarrow-up-right capabilities while granting businesses granular control over the user journey. By utilizing Server-to-Server (S2S) APIs and unique identifiers payment_method_id, businesses can separate the collection of payment credentials from the actual transaction logic.

The Two-Step Integration Pattern

  1. Credential Capture & Vaulting

The business initiates the flow by capturing payment details (such as cards, wallets, or bank accounts) using either the Payment Method SDK or the /payment-methods API. This process securely vaults the payment instrument and generates a unique payment_method_id.

  1. Transaction Execution

Once the payment_method_id is generated, it serves as a reusable token (learn more). The business can pass this ID into the /payments API to execute any supported payment functionality—including one-click checkouts, recurring charges, or manual captures—without re-collecting sensitive data.

Last updated

Was this helpful?