Download the PHP package se7enxweb/sevenx_payment_stripe without Composer
On this page you can find all versions of the php package se7enxweb/sevenx_payment_stripe. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download se7enxweb/sevenx_payment_stripe
More information about se7enxweb/sevenx_payment_stripe
Files in se7enxweb/sevenx_payment_stripe
Package sevenx_payment_stripe
Short Description Stripe Payment Element gateway for eZ Publish 4 / Exponential CMS. Integrates the Stripe PaymentIntents API and Stripe.js Payment Element into the eZ Publish shop workflow. Supports cards, Apple Pay, Google Pay, Link, Stripe Tax, and all Stripe-enabled payment methods.
License GPL-2.0-or-later
Homepage https://github.com/se7enxweb/sevenx_payment_stripe
Informations about the package sevenx_payment_stripe
7x Payment Gateway : Stripe
A Stripe payment gateway extension for Exponential. Provides an alternative payment gateway using the modern Stripe Payment Element — a single, embedded UI that supports cards, Apple Pay, Google Pay, Link, and every Stripe-supported payment method with zero additional code.
At a glance
| Extension name | sevenx_payment_stripe |
| Version | 1.0.0 |
| License | GNU General Public License v2.0 (or any later version) |
| Requires | Exponential CMS 4.7+ · PHP 8.0+ · Composer · ezjscore extension |
| ezjscore | Latest version — must be installed, activated, and working |
| Stripe PHP SDK | stripe/stripe-php v14+ (installed via Composer) |
| Stripe.js | v3 (loaded from https://js.stripe.com/v3/) |
| Tested on | PHP 8.2, Exponential CMS 4.7 |
How it works
The extension integrates with the Exponential shop workflow event system. When a customer reaches the payment step, Exponential calls loadForm() on the gateway class, which renders the Stripe Payment Element. After Stripe confirms the payment in-page, the JS posts to ezjsc-stripe::verify which verifies the result server-side and marks the order as Paid (status 1000). The browser then navigates to a clean /shop/checkout URL where the workflow advances automatically.
Payment flow
Step-by-step
loadForm()—Sevenx_Payment_StripeGateway::loadForm()checks whether the order is already at status 1000 (Paid). If so it returnsSTATUS_ACCEPTEDimmediately. If not, it rendersstripe_form.tplcontaining the Stripe Payment Element and returnsSTATUS_FETCH_TEMPLATE_REPEAT.POST ezjsc-stripe::confirm—stripe-checkout.jsposts{"orderId": <int>}to this eZJSCore endpoint.ezjscServerFunctionsStripeJs::confirm()validates ownership, calculates order totals, optionally calls the Stripe Tax API, and creates aPaymentIntent. Returns{"error_text":"","content":{"clientSecret":"..."}}to the browser.stripe.confirmPayment()— Stripe.js collects the payment method, handles 3D Secure challenges in-page (redirect: "if_required"). Cards and most methods succeed without leaving the page. Methods that require a redirect usereturn_url: window.location.origin + "/shop/checkout"so the verify step runs on return.POST ezjsc-stripe::verify— OnpaymentIntent.status === 'succeeded'(or on redirect-back viacheckStatus()), the JS posts{"paymentIntentId": "pi_..."}.ezjscServerFunctionsStripeJs::verify()retrieves thePaymentIntentfrom Stripe server-side (never trusting client data alone), confirmsstatus === 'succeeded'andmetadata.order_idmatches, then calls$order->modifyStatus(1000)which records the status change atomically.- Workflow completion — The JS calls
window.location.replace("/shop/checkout")— a clean URL with no Stripe query parameters. Exponential callsloadForm()again; it detectsstatus_id === 1000and returnsSTATUS_ACCEPTED, advancing the workflow to the order confirmation page.
Quick start
See doc/INSTALL.md for complete requirements and installation steps.
Documentation
| Document | Contents |
|---|---|
| doc/INSTALL.md | Requirements, installation, Composer setup, INI configuration |
| doc/FEATURES.md | Full feature list — security, Stripe Tax, Payment Element |
| doc/FAQ.md | Troubleshooting and common questions |
| doc/TODO.md | Roadmap and planned improvements |
| doc/EZCURLGATEWAY.md | eZCurlGateway PHP 8 fork — diff vs stock, rationale |
| doc/changelogs/ | Version history |
Extension structure
Configuration
INI settings — settings/override/stripe.ini.append.php
Set real keys in the site-level override (never in the extension's own settings/stripe.ini.append.php, which is committed to version control and contains only placeholders).
Find your keys at https://dashboard.stripe.com/apikeys.
Going live (test → production)
- Replace both
SecretKeyandPublishableKeyinsettings/override/stripe.ini.append.phpwith yoursk_live_...andpk_live_...keys. Both must be from the same Stripe account. - Confirm
window.location.origin + "/shop/checkout"resolves correctly for your domain — this is thereturn_urlused for redirect-required payment methods (iDEAL, 3DS fallback, etc.). - If using Stripe Tax, verify that Tax is activated in the Stripe Dashboard for your account.
- Test end-to-end in the Stripe Dashboard with a live card before announcing production.
Requirements summary
- Exponential 6.0.x+ (PHP 8.2+)
- PHP 8.0 or higher
- ezjscore extension — latest version, installed and activated (the AJAX endpoints
ezjsc-stripe::confirmandezjsc-stripe::verifyare registered via ezjscore'sFunctionListmechanism; without it no payment can be initialised or verified) - Composer (for the
stripe/stripe-phpSDK) - A Stripe account (free — stripe.com)
- HTTPS on the production domain (required by Stripe for live payments)
License
Copyright (C) 2001–2026 7x. Released under the GNU General Public License v2.0 (or any later version) — see LICENSE.