Skip to main content
Stripe supports card payments through its global acquiring platform.

​
Setup

Follow the Stripe setup instructions before configuring card payments.

​
Supported countries

​
Supported currencies

​
Limitations

Additional limitations include:
  • Partial captures require cart items - If the authorization request includes cart_items, every subsequent partial capture for that transaction must also include at least one cart item. The cart item doesn’t need to match one included in the original authorization or in a previous capture.

​
Integration

To accept card payments with Stripe, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which automatically routes the payment to your configured Stripe connection based on your Flow rules or explicit payment_service_id parameter.

​
Generating Stripe Tokens

When standalone tokenization is performed via our POST /payment-methods API, Gr4vy’s integration uses Stripe’s Payment Method API. This tokenizes the card with Stripe without performing any kind of cardholder authentication. For European cards, this doesn’t fulfill Strong Customer Authentication (SCA) requirements and therefore you may see decreased conversion on those cards for recurring payments. In contrast, when the store=true flag is utilized to vault a card during a transaction, the process uses the Stripe Setup Intents API. This API runs an actual authorization and guarantees that the resulting token meets SCA requirements and is ready to be used for MIT. Zero-value authentication is recommended if you want to vault a card and re-use it in SCA markets.