|
| 1 | +--- |
| 2 | +keywords: ['deployment', 'issues', 'integration'] |
| 3 | +slug: /deployment-issues-with-stripe-integration |
| 4 | +title: Deployment Issues with Stripe Integration |
| 5 | +--- |
| 6 | +# Deployment Issues with Stripe Integration |
| 7 | + |
| 8 | +Integrating Stripe in your FlutterFlow project can help you accept payments efficiently. However, some common deployment issues may arise. This article outlines key steps and best practices to ensure a smooth Stripe integration and deployment experience. |
| 9 | + |
| 10 | +1. **Firebase Connection** |
| 11 | + |
| 12 | + Stripe integration requires a connected Firebase project. Before running through this checklist, it's important to ensure your FlutterFlow project is linked to Firebase, a crucial step for successful payment processing. Detailed guidance can be found at [FlutterFlow's Firebase Setup Guide](https://docs.flutterflow.io/data-and-backend/firebase/firebase-setup). |
| 13 | + |
| 14 | +2. **Upgrade to Firebase Blaze Plan** |
| 15 | + |
| 16 | + Stripe functionality requires a Firebase Blaze Plan for operational capabilities. To avoid disruptions, you will need to upgrade from the Firebase Spark plan to the Blaze plan. Learn more about Google's process for upgrading [here](https://firebase.google.com/docs/projects/billing/firebase-pricing-plans). |
| 17 | + |
| 18 | +3. **Set the Google Cloud Platform (GCP) Location** |
| 19 | + |
| 20 | + A defined Google Cloud Platform (GCP) location for your Firebase project ensures the correct regional operation of services. The absence of a set location can hinder the deployment process. |
| 21 | + |
| 22 | +  |
| 23 | + |
| 24 | +4. **Firebase Project Permissions** |
| 25 | + |
| 26 | + Ensure you have the necessary permissions enabled for your Firebase project. Two critical permissions involve access management and service configuration. You can reference the [setup guide](https://docs.flutterflow.io/data-and-backend/firebase/firebase-setup)on FlutterFlow Documentation on FlutterFlow Documentation. |
| 27 | + |
| 28 | +  |
| 29 | + |
| 30 | +5. **Correct Merchant Code** |
| 31 | + |
| 32 | + Use the correct 3-letter merchant country code (e.g., "GBR" for the United Kingdom vs. "UK"). Incorrect codes can lead to failed transactions. For accurate codes, refer to [IBAN Country Codes](https://www.iban.com/country-codes). |
| 33 | + |
| 34 | +  |
| 35 | + |
| 36 | +  |
| 37 | + |
| 38 | +6. **Test and Live Keys** |
| 39 | + |
| 40 | + For deployment, both Test and Live Stripe keys must be configured in your project settings, regardless of the development stage. This ensures Stripe's API can properly interact with your application. |
| 41 | + |
| 42 | +  |
| 43 | + |
| 44 | +7. **Consistent Region Settings** |
| 45 | + |
| 46 | + Align your Firebase project's region with that of your FlutterFlow settings to prevent deployment failures. Inconsistencies can cause function deployment issues. |
| 47 | + |
| 48 | +  |
| 49 | + |
| 50 | +  |
| 51 | + |
| 52 | +If you find that this article hasn't fully addressed your concerns or if you have more questions, please don't hesitate to reach out to us at [email protected] |
| 53 | + |
| 54 | + |
0 commit comments