Overview of Stripe payment gateway integration

Supported features

The following table provides a quick reference for the supported features. For details about each feature, see the later sections in this article.

Supported payment methods

The following table lists the supported payment methods for each Stripe integration version:

For more information about setting up payment methods in Zuora, see Define and set up payment methods.

The following sections provide additional information for each payment method.

Payment/Refund status for Stripe v2

When processing a payment or refund through an asynchronous payment method such as bank transfer and ACH, the status "Processed" in Zuora indicates that the payment or refund processing request has been successfully submitted to the Stripe v2 gateway. To get to know the final status of the payment or refund, you need to integrate the Stripe Webhook service.

Support for 3D Secure 2.0

See Enable 3DS2 for Stripe gateway integration and Zuora’s implementation of 3D Secure 2.0 for more information.

Support for Delayed Capture

You can use the Delayed Capture feature to authorize available funds for a transaction but delay the capture of funds until a later time. Zuora's Stripe v2 gateway integrations support Delayed Capture for credit card payment methods. You can use the Create authorization API operation to authorize a payment amount before capturing the payment. Subsequently, you can use Create a payment to fully or partially capture the authorized amount, or use Cancel authorization to cancel the authorization. 

Note that you can perform only one capture on an authorized payment. If you partially capture a payment, you cannot perform another capture.

Support for Level 2 and Level 3 card data

Stripe v2 supports processing Level 2 and Level 3 credit card data. For more information, see the following articles:

• Level 2 and Level 3 Card Data
• Set up and configure a Stripe payment gateway instance

Support for stored credential profiles

Stripe v2 includes support for the Stored Credential Transactions framework. For details about the supported payment methods, see Support for stored credential transactions overview.

Supported Gateway Options fields

You can submit additional information to the Stripe gateway by using the Gateway Options fields. The Stripe v2 gateway integration supports the following Gateway Options fields.

Support for MOTO transactions

Credit card payment transactions through Stripe v2 can be processed as Mail Order Telephone Order (MOTO) payment transactions. When creating a payment through the UI or API operation, you can specify the following field with MOTO. The MOTO transaction indicator will be included in the request to the gateway and a recurring stored credential profile will be created for the payment method used to process the payment. The network transaction ID (NTI) will be returned in the authorization response.

You can also use MOTO transactions to create stored credential profiles when creating credit card payment methods through UI or processing recurring card payment transactions. For details, see the following articles:

• Create credit card payment methods through UI
• Migrate all existing payment methods for stored credential transactions

Known Issue and Workaround

When creating a payment method, if the following error message is returned from Stripe, log in to the Stripe dashboard and enable Handle card information directly.

{ "error":
    {
        "message": "Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing.",
        "type": "invalid_request_error"
    }
} 

Because both Zuora and Stripe are PCI compliant, there is no security issue if Handle card information directly is enabled.

Related information

Set up and configure a Stripe payment gateway instance