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 sections provide additional information for each supported payment method type.

For more information about the supported currencies, see Supported currencies by gateways.

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

{
   "accountKey": "402881868ab1b937018ab2314b91234a",
   "bankCode": "10880",
   "accountHolderInfo": {
            …
    },
    "type": "Bacs",
    "accountMaskNumber": "****2345",
    "tokens": {
        "gatewayType": "Stripe",
        "tokenId": "testTokenId",
        "secondTokenId": "testSecondTokenId"
    }
}

{
    "accountNumber": "00012345",
    "accountKey": "402881868ab1b937018ab2314b91234a",
    "bankCode": "10880",
    "accountHolderInfo": {
            …
    },
    "type": "Bacs",
    "gatewayOptions": {
         "ipAddress": "3:3:3:3:3:3:2:1",
         "UserAgent": "Test123456"
    }
}

Payment/Refund Processing

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.

While creating recurring off-session payments without 3DS2, Zuora does not create customer accounts on the Stripe side. Zuora creates customer accounts on the Stripe side for the following transactions:

• One-time on-session payments
• Recurring off-session payments with 3DS2

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

The Delayed Capture feature allows you to authorize the availability of funds for a transaction but delay the capture of funds until a later time. The Stripe v2 gateway integrations support Delayed Capture for Credit Card payment methods. For how to use the Delayed Capture feature, see Payment Authorization in Zuora API Reference.

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.

Support for Stripe Radar

If Stripe Radar is enabled in both Stripe and Zuora, Zuora uses Stripe client-side SDK to collect the Radar Session ID and pass it to Stripe. Credit Card and Credit Card Reference payment transactions sent to Stripe from Zuora will be assessed for fraudulent activity by Stripe Radar. To enable the support for Stripe Radar in Zuora, submit a ticket at Zuora Global Support.

You can use Additional Metadata and Gateway Options fields to build your custom Stripe Radar rules. To disable the support for Stripe Radar in Zuora, see Set up and configure a Stripe payment gateway instance.

Support for Real-Time Reconciliation

Stripe v2 supports the Real-Time Reconciliation feature. With this feature enabled, the payment gateway can submit notifications to Zuora for various event types on gateway objects, and the corresponding records can be automatically updated in real time.

1. For information about how to enable Real-Time Reconciliation and the limitation, see Real-Time Reconciliation.

2. For information about the supported events for Stripe v2 and the corresponding actions from Zuora, See Real-Time Reconciliation events for Stripe v2.

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.

"gatewayOptions": {
    "RadarSessionId": "rse_1N7fvKSDx60UgxZnDB5Hb4v5" 
}

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 Manage stored credential profiles.

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