by Lazy Sloth

Stripe page for Wordpress

Test this app for free
55
Test this app for free
55 
import os
import logging
from fastapi import FastAPI, HTTPException
from fastapi.middleware.cors import CORSMiddleware
from pydantic import BaseModel, Field
import stripe
import uvicorn

# Constants
STRIPE_SECRET_KEY = os.environ['STRIPE_SECRET_KEY']
YOUR_DOMAIN = os.environ['YOUR_DOMAIN']

# Configure Stripe API key
stripe.api_key = STRIPE_SECRET_KEY

# FastAPI app initialization
app = FastAPI()

# CORS configuration
origins = ["*"]
app.add_middleware(
    CORSMiddleware,
    allow_origins=origins,
    allow_credentials=True,
Get full code

Created: | Last Updated:

This app integrates a custom Stripe payment page in WordPress. It includes both a backend and a frontend. The backend service is set up using FastAPI and is compatible with any price point established through the Stripe API. The backend service creates a Stripe checkout session and retrieves the status of a checkout session. It also allows all CORS and logs sent requests and checkout session statuses. The price ID is fetched during the request from the user. After adding the Stripe API key and directing the backend service to the price ID, the backend service can be activated by clicking the test button. The frontend code can be integrated into a WordPress page to create a custom payment page in WordPress. This method can be used to set up various types of payment pages in WordPress, including one-time payments and subscriptions. The required environment secrets for this app are STRIPE_SECRET_KEY and YOUR_DOMAIN.

Introduction to the Stripe Integration Template for WordPress

This template is designed to help you integrate Stripe payment processing into a WordPress site. It provides a backend service using FastAPI to create and manage Stripe checkout sessions, and frontend code to embed the Stripe checkout experience into your WordPress page. This guide will walk you through the steps to set up and use this template on the Lazy platform.

Getting Started

To begin using this template, click "Start with this Template" on the Lazy platform. This will pre-populate the code in the Lazy Builder interface, so you won't need to copy or paste any code manually.

Initial Setup

Before testing the app, you'll need to set up some environment secrets within the Lazy Builder:

  • STRIPE_SECRET_KEY: Your Stripe secret API key. You can find this in your Stripe dashboard under Developers > API keys.
  • YOUR_DOMAIN: The domain of your website where the Stripe checkout will be redirected after payment. For example, "https://www.yourwebsite.com".

These values are not stored in your operating system but are set in the Environment Secrets tab within the Lazy Builder.

Test: Pressing the Test Button

Once you have set up the environment secrets, press the "Test" button in the Lazy Builder. This will deploy the app and launch the Lazy CLI. If the code requires any user input, you will be prompted to provide it through the Lazy CLI.

Entering Input

If the code requires user input, you will be prompted for it after pressing the "Test" button. Follow the instructions in the Lazy CLI to enter the necessary information.

Using the App

After deployment, Lazy will provide you with a dedicated server link to use the API. If you're using FastAPI, Lazy will also provide a link to the API documentation.

Integrating the App into WordPress

To integrate the backend service into your WordPress site, you'll need to add the provided frontend code to your WordPress payment page. Here's how:

  1. Log in to your WordPress dashboard and navigate to the page where you want to add the payment functionality.
  2. Edit the page and insert the provided frontend script just before the </body> tag.
  3. Replace "PUBLISHABLE STRIPE API KEY" with your actual publishable API key from Stripe.
  4. Replace "LAZY SERVER LINK" with the endpoint URL of your published app that you received after pressing the "Test" button.
  5. Replace "PRICE_ID" with the actual price ID you want to use for the transaction. You can find this in your Stripe dashboard under Products.

Here is the script you need to add to your WordPress page:

`

` After adding this script to your WordPress page, your custom Stripe payment page will be ready to accept payments.

Remember to test the payment flow thoroughly to ensure everything is working as expected before going live with your new payment page.

Technologies

WordPress WordPress
Streamline Stripe Payments with Lazy AI Templates: Automate Billing, Invoices, Payments and More Streamline Stripe Payments with Lazy AI Templates: Automate Billing, Invoices, Payments and More
FastAPI Templates and Webhooks FastAPI Templates and Webhooks

Similar templates

FastAPI endpoint for Text Classification using OpenAI GPT 4

This API will classify incoming text items into categories using the Open AI's GPT 4 model. If the model is unsure about the category of a text item, it will respond with an empty string. The categories are parameters that the API endpoint accepts. The GPT 4 model will classify the items on its own with a prompt like this: "Classify the following item {item} into one of these categories {categories}". There is no maximum number of categories a text item can belong to in the multiple categories classification. The API will use the llm_prompt ability to ask the LLM to classify the item and respond with the category. The API will take the LLM's response as is and will not handle situations where the model identifies multiple categories for a text item in the single category classification. If the model is unsure about the category of a text item in the multiple categories classification, it will respond with an empty string for that item. The API will use Python's concurrent.futures module to parallelize the classification of text items. The API will handle timeouts and exceptions by leaving the items unclassified. The API will parse the LLM's response for the multiple categories classification and match it to the list of categories provided in the API parameters. The API will convert the LLM's response and the categories to lowercase before matching them. The API will split the LLM's response on both ':' and ',' to remove the "Category" word from the response. The temperature of the GPT model is set to a minimal value to make the output more deterministic. The API will return all matching categories for a text item in the multiple categories classification. The API will strip any leading or trailing whitespace from the categories in the LLM's response before matching them to the list of categories provided in the API parameters. The API will accept lists as answers from the LLM. If the LLM responds with a string that's formatted like a list, the API will parse it and match it to the list of categories provided in the API parameters.

Icon 1 Icon 1
251
Stripe Webhook FastAPI Test Sender

By leveraging FastAPI, this template will send and test the mock webhook received from the Stripe API. Stripe Webhook test will print the data on the console.

Icon 1 Icon 1
231
Gmail Email Sender App

This app securely connects to GMAIL via SMPT app and sends a test email. It can be used as a basic building block to build more complicated email sending apps.

Icon 1
187
Create Stripe Payment Intent with API

This app template will create and retrieve a payment intent on Stripe using API. It requires the Stripe API key to be set as an environment variable named 'STRIPE_API_KEY'. The template provides a POST endpoint at '/create_payment_intent' to create a payment intent and a GET endpoint at '/retrieve_payment_intent/{payment_intent_id}' to retrieve a payment intent.

Icon 1 Icon 1
94
Jira Weekly Done Issues to Slack

This app provides a summary of completed Jira tasks posted to a specific Slack thread every week. It uses the Jira API to download closed tickets from the current week. The query filters for tickets with the status 'Done' and last updated this week. The ticket details, including the ticket URL, are posted to Slack in a single thread. The required environment variables are JIRA_DOMAIN, JIRA_EMAIL, JIRA_API_TOKEN, SLACK_TOKEN, and SLACK_CHANNEL.

Icon 1 Icon 1
80
Gmail Organization Invitation API

This app is an API that sends an invitation email from a Gmail account with 2FA enabled. It accepts various inputs to generate a personalized invitation email based on the name of the email of the person being invited, the email who invited the person and the name of the organisation and an invitation link.

Icon 1
68
Send a daily report of some metrics from BigQuery to Slack

This app fetches data from BigQuery using a provided SQL query, formats the data into a table, and posts the table to a specified Slack channel. The data posting is scheduled to happen every day at 10 am UK time.

Icon 1 Icon 1 Icon 1
44
Create Stripe Checkout Session with API

<p>This application serves as an API server that incorporates functionalities. It includes an endpoint that allows you to create a Stripe checkout session, for payment processing. Additionally it provides another endpoint to retrieve the status of a checkout session. The application allows for origin resource sharing (CORS) and generates logs with information level details regarding sent requests.</p><p>‍</p>

Icon 1 Icon 1
43
Webflow Collection Item Blog Post Draft API

The Webflow Blog Post Publisher is an app that provides an API endpoint to publish blog posts on Webflow as a draft. The API accepts all necessary information to create a blog post, including the Webflow API token. It also accepts extra fields that will be sent to Webflow as part of the fieldData. The name of the new item added to the collection will be the post_name provided in the request. The slug of the new item will be derived from the post_name by replacing spaces with underscores. The API accepts optional fields in the BlogPostData for extra_fields. All the optional fields will be part of the dictionary extra_fields. All the variables in the extra_fields are converted to kebab-case before they are passed into fieldData. The optional fields inside extra_fields variable are post_body, thumbnail_image, main_image, and post_summary. The app requires two environment variables to function properly: WEBFLOW_API_TOKEN and COLLECTION_ID. The post is linked with the collection in Webflow. The COLLECTION_ID environment variable is the ID of the collection in Webflow where the post will be added.

Icon 1
42

We found some blogs you might like...