Stripe integration guide

Stripe logo Stripe is a gateway that allows you to collect card payments. This guide is intended to help you implement Stripe based on your preferred integration workflow.

Services and compatibility

Supported payment types
  • Card
Supported transaction types
  • Sale (saved card token or full card number) ( API )
  • Auth Only (saved card token or full card number) ( API )
  • Capture (partial supported) ( API )
  • Void ( API )
  • Refund (partial and multiple) ( API )
Supported processing currenciesAED, AFN, ALL, AMD, ANG, AOA, ARS, AUD, AWG, AZN, BAM, BBD, BDT, BGN, BIF, BMD, BND, BOB, BRL, BSD, BWP, BZD, CAD, CDF, CHF, CLP, CNY, COP, CRC, CVE, CZK, DJF, DKK, DOP, DZD, EGP, ETB, EUR, FJD, FKP, GBP, GEL, GIP, GMD, GNF, GTQ, GYD, HKD, HNL, HRK, HTG, HUF, IDR, ILS, INR, ISK, JMD, JPY, KES, KGS, KHR, KMF, KRW, KYD, KZT, LAK, LBP, LKR, LRD, LSL, MAD, MDL, MGA, MKD, MMK, MNT, MOP, MRU, MUR, MVR, MWK, MXN, MYR, MZN, NAD, NGN, NIO, NOK, NPR, NZD, PAB, PEN, PGK, PHP, PKR, PLN, PYG, QAR, RON, RSD, RUB, RWF, SAR, SBD, SCR, SEK, SGD, SHP, SLL, SOS, SRD, STN, SZL, THB, TJS, TOP, TRY, TTD, TWD, TZS, UAH, UGX, USD, UYU, UZS, VND, VUV, WST, XAF, XCD, XOF, XPF, YER, ZAR, ZMW
3D Secure 1.x supportedYes
3D Secure 2.x supportedNo
External 3D Secure supportedNo
Installments supportedNo

Gateway-specific information

The following are not supported with Stripe:

  • paymentType is not supported.
  • Recurring billing

Configuration

Work with Integrations Support to add Stripe as a connection. You will need the following credentials from Stripe (https://dashboard.stripe.com/login):

  • Publishable Key
  • Secret Key

Required fields

The following fields are required when processing a payment request with Stripe:

  • card.cardHolderName
  • data.amount
  • data.currency
  • data.customer.firstName
  • data.customer.lastName
  • data.customer.shipToAddressOne

Testing data

Use the following test card information to test your Stripe configuration.

BrandCard numberExpiration dateSecurity codeCardholder nameTransaction result
Visa4111111111111111Any111AnySuccess
Visa4242424242424242AnyAnyAnySuccess
Visa (debit)4000056655665556AnyAnyAnySuccess
Mastercard5105105105105100Any111AnySuccess
Discover6011111111111117Any111AnySuccess
Visa4000000000000002Any111AnyDecline
Amex378282246310005Any737AnyInsufficient funds
Visa4000000000000069Any7373AnyCard expired
Visa4000000000000127Any737AnyIncorrect security code
Visa (3DS1)4000002760003184Any737AnySuccess
Visa (3DS1)4000008400001629Any7373AnyDecline
Visa (3DS1)4000008260003178Any737AnyInsufficient funds

Status workflows

The status of a successful transaction with Authorize.net varies, depending on the options you choose.

SaleWhen isAuthOnly is false, successful sale transactions will have the following statuses:
  • pending* or authorized
  • settled
Auth onlyWhen isAuthOnly is true, successful sale transactions will have the following status:
  • authOnly
CaptureSuccessful capture transactions will have the following statuses:
  • pending* or authorized
  • settled
VoidSuccessful void transactions will have the following status:
  • voided
RefundSuccessful refund transactions will have the following statuses:
  • pending* or authorized
  • settled

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the appropriate transactionStatus table).

If you have any additional questions or feedback, contact us.