Enumerations

The result of an attempt to confirm a PaymentIntent or SetupIntent

Errors specific to PaymentSheet itself

Most errors do not originate from PaymentSheet itself; instead, they come from the Stripe API or other SDK components like STPPaymentHandler, PassKit (Apple Pay), etc.

What set of billing address information you need to collect from your user.

@note If the user is from a country that does not use zip/postal codes, the user may not be asked for one regardless of this setting.

Possible validation states for a bank account.

Error codes generated by STPBankAccountCollector

The type of entity that holds a bank account.

The payment methods supported by STPBankSelectionViewController.

These values control the labels used in the shipping info collection form.

An enum representing the status of a shipping address validation.

An enum representing the status of a payment requested from the user.

An enum representing the success and error states of PIN management

The various funding sources for a payment card.

The various card brands to which a payment card can belong.

Options for configuring the display of an STPCardFormView instance.

These fields indicate whether a card field represents a valid value, invalid value, or incomplete value.

The business type of the Connect account.

The various bank brands available for FPX payments.

The purpose of the uploaded file.

Types of next actions for STPPaymentIntent and STPSetupIntent. You shouldn’t need to inspect this yourself; STPPaymentHandler will handle any next actions for you.

The type of the Klarna line item.

The type of customer acceptance information included with the Mandate.

STPPaymentHandlerActionStatus represents the possible outcomes of requesting an action by STPPaymentHandler. An action could be confirming and/or handling the next action for a PaymentIntent.

Error codes generated by STPPaymentHandler

Capture methods for a STPPaymentIntent

Confirmation methods for a STPPaymentIntent

Status types for an STPPaymentIntent

Indicates how you intend to use the payment method that your customer provides after the current payment completes. If applicable, additional authentication may be performed to comply with regional legislation or network rules required to enable the usage of the same payment method for additional payments.

Types of Actions from a STPPaymentIntent, when the payment intent status is STPPaymentIntentStatusRequiresAction.

Types of Source Actions from a STPPaymentIntent, when the payment intent status is STPPaymentIntentStatusRequiresSourceAction. @deprecated UseSTPPaymentIntentActionType instead.

The type of the error represented by STPPaymentIntentLastPaymentError. Some STPPaymentIntentLastPaymentError properties are only populated for certain error types.

The result of a check on a Card address or CVC.

The type of Card Wallet.

The type of the PaymentMethod.

Account holder type

Account type

Error codes specific to STPRedirectContext

Possible states for the redirect context to be in

Status types for an STPSetupIntent

Indicates how the payment method is intended to be used in the future.

The type of the error represented by STPSetupIntentLastSetupError. Some STPSetupIntentLastError properties are only populated for certain error types.

The status of this card’s 3D Secure support.

Authentication flows for a Source

Usage types for a Source

Status types for a Source

Types for a Source

Custom payment methods for Klarna

Redirect status types for a Source.

Verification status types for a Source.

An enum that defines the different types of buttons that are able to be customized.

An enumeration of the case transformations that can be applied to the button’s title

Possible Token types

Possible error code values for NSErrors with the StripeDomain domain

Possible string values you may receive when there was an error tokenizing a card. These values will come back in the error userInfo dictionary under the STPCardErrorCodeKey key.