Stripe
API Version
Minimum required API version: 1.1.0
Payment Methods
The following table lists all supported payment methods.
Payment Method | Payment Method Type |
---|---|
American Express | Cards |
DINERS | Cards |
DISCOVER | Cards |
JCB | Cards |
MASTERCARD | Cards |
VISA | Cards |
Currencies
See the Stripe documentation.
Features
The following table provides an overview of all supported and non-supported features.
Feature | Supported |
---|---|
3DS 2.0 External | No |
3DS 2.0 PaymentsOS-handled | No |
3DS 2.0 Provider-handled | No |
3DS 2.0 Self-handled | No |
Installments | No |
Level 2 and 3 Data | No |
Multi-seller Payments | No |
Network Tokens | No |
Payment Facilitator | No |
PayU Risk | No |
Pre-authorization | No |
Retrieve Supported Payment Methods | No |
Retrieve Supported Plans | No |
Statement Soft Descriptor | Yes |
Stored Credentials Flag | No |
Transaction Processing without CVV | Yes |
Requests
The following table lists all supported requests for card-based transactions. Use the bodybuilder to create a sample request body for each request type.
Request | Partial/Multiple | Mode |
---|---|---|
Authorize | Partial and multiple are not supported | Synchronous |
Capture | Partial is supported | Synchronous |
Charge | Not Applicable | Synchronous |
Refund | Both partial and multiple are supported | Synchronous |
Void | Not Applicable | Synchronous |
Setup Procedures
The following table lists the setup procedures that are specific to this provider.
Configuration | Required/Optional |
---|---|
In the PaymentsOS Control Center, configure the following credentials:
| Required |
Allow Stripe to safely accept tokens from PaymentsOS. For help, see Allowing Stripe to Safely Accept Tokens from PaymentsOS below. | Required |
Integration Procedures
The following sections list the integration procedures that are specific to this provider.
Allowing Stripe to Safely Accept Tokens from PaymentsOS
PaymentsOS is PCI DSS compliant, guaranteeing that all card data is securely stored. Stripe, however, is unaware of this PCI DSS compliancy accreditation when receiving tokens from PaymentsOS and will thus assume that you are sending credit card numbers directly to its API (which is considered to be unsafe). As a result, you will receive the following error in the provider_data
object in the response data of your transaction request:
{
"provider_data": {
"provider_name": "Stripe",
"response_code": "StripeInvalidRequestError",
"description": "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.",
}
}
To circumvent this, you must configure Stripe to allow unsafe transactions. To do so, login to your Stripe dashboard. Then navigate to Business Settings > Integration and toggle on the Process payments unsafely option. You will be asked to confirm that you know what you are doing before you can apply the setting.
Support for Radar
Radar is currently not supported when integrating with Stripe.
Testing
Use the Test Cards in the Test card numbers and tokens page for testing.