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

​
Setup

Follow the Stripe setup instructions before configuring card payments.

​
Capabilities

This connector supports the Mastercard Transaction Link Identifier (TLID), with nothing to enable. In an open-loop configuration, Gr4vy stores the TLID from the first customer-initiated payment and sends it on later merchant-initiated payments. In the default closed-loop configuration, cards are stored with Stripe, which keeps and replays the TLID itself.

​
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.
  • No Interac cards - Interac debit cards, including Interac cards in Apple Pay, can’t be processed. Stripe requires Interac payments to be authorized and captured in one request, and this connector always authorizes and captures in separate steps. Setting intent to capture doesn’t change this.

​
3-D Secure

To use 3-D Secure results from Gr4vy, or your own external 3-D Secure data, Stripe must enable 3DS Import on your account. See 3DS Import.

​
Cart items

Gr4vy sends cart_items to Stripe as line items on the authorization and on each capture. The item sku becomes Stripe’s product_code, and unit_of_measure is sent unchanged. Gr4vy doesn’t shorten these values, and Stripe rejects the request when a value is longer than Stripe allows. According to Stripe’s API reference, product_code and unit_of_measure take at most 12 characters each.

​
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 - Embed SDKs for iOS, Android, and React Native
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 the 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.