Question 1

How to install vapor-community/stripe-provider in a Vapor project?

Accepted Answer

Add the package to your Package.swift file with the provided URL and version, then set the STRIPE_API_KEY environment variable. The library automatically integrates with Vapor's request system for easy access.

Question 2

Stripe-provider vs using StripeKit directly in Vapor?

Accepted Answer

Stripe-provider adds convenience by wrapping StripeKit into Vapor's Request objects for tighter integration, while StripeKit offers more direct API control. Choose stripe-provider for faster setup in standard Vapor apps, but StripeKit if you need lower-level customization.

Question 3

How to handle Stripe webhooks with this library?

Accepted Answer

The library doesn't include built-in webhook support; you must implement webhook endpoints manually in Vapor routes, verifying signatures with StripeKit and handling events like payment failures separately.

Question 4

Is this library production-ready for e-commerce?

Accepted Answer

Yes, it's used in production by community projects, but due to limited documentation, ensure thorough testing of payment flows and error scenarios, and consider customizing for complex transaction needs.

Question 5

How to manage recurring subscriptions with stripe-provider?

Accepted Answer

Use the StripeClient methods for subscription APIs via req.stripe, but the README lacks examples, so refer to StripeKit's documentation and implement custom logic for billing cycles and plan management.

Question 6

What's the error handling like in this library?

Accepted Answer

It relies on StripeKit's error types and Swift's try-catch blocks; the library doesn't add custom error handling, so you need to map Stripe errors to appropriate HTTP responses, as hinted in the chargeCustomer example's status checks.

Stripe Provider

What is Stripe Provider?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions