money-bill-1-wavePayment Processor Capabilities

A technical reference for the parameters and lifecycle flows supported across card and wallet integrations.

Core Payment Flows

Hyperswitch supports a wide range of parameters through the Payments Create API for the underlying payment connectors it integrates with. The diagram below illustrates the various parameters and flows supported as part of a typical payment connector integration.

Card Payment Flow Configurations

Hyperswitch enables multiple card payment configurations designed to support a wide range of industry-specific use cases through the unified Payment Confirmarrow-up-right request.

  • Verification: Facilitates $0 verification, $0 verification for subscriptionsarrow-up-right, and AVS & CVV integrity checks.

  • Authentication: Modular support for External authentication providers or native PSP authentication.

  • Capture Strategy: Configuration for Automatic capturearrow-up-right or Manual/Multiple manual capture logic.

  • Voiding: Explicit support for Voids initiated both before capture and before settlement.

Card-Specific Parameters

The Payments API supports an extensive set of card parameters to ensure regional flexibility and compliance across retail and subscription billing.

Transaction Initiation Types

  • Customer Initiated (CIT): Supports Raw Cardarrow-up-right and Network Token inputs.

  • Merchant Initiated (MIT): Optimized for recurring billing using Processor Tokens, Raw Card + NTID, or Network Token + NTID.

  • Agent Initiated: Securely handle Shared Payment Tokens for delegated payment scenarios.

Advanced Data Fields

  • Pre-transaction: Integration of 3DS Authentication Dataarrow-up-right and Risk/Fraud check data.

  • Order Metadata: Deep support for L2/L3 data fields, full order information, and complex Routing Dataarrow-up-right.

  • Additional Flags: granular control for Moto, Estimated Auth, Incremental Auth, and Partial Authorizations.

Digital Wallet Integration

Hyperswitch provides comprehensive parameters that streamline transaction management across leading digital wallets like Google Pay and Apple Pay.

  • Experience Models: Support for Native, Redirect, and 3rd-party SDK integration patterns to ensure a seamless checkout experiencearrow-up-right.

  • Payload Management: Robust handling of both Decrypted (with cryptogram and wallet data) and Encrypted payment data payloads.

Post-Transaction: Refunds, Disputes, and Errors

Hyperswitch offers a unified interface to track, respond to, and reconcile outcomes across multiple PSPs from a single orchestration layer.

Last updated

Was this helpful?