Skip to content
  • Our Product
    • Namazu Elements
      • What is Elements?
      • Why open source?
      • Docs
        • Namazu Elements in Five Minutes or Less
        • RESTful APIs Library
        • Security Model
        • Accessing the Web UI (CMS)

    Our Product

    A logomark with three layered rhombuses adorning the lettermark that says Elements in bold all-caps sans-serif letters.
    • What is Namazu Elements? Discover our easy-to-use backend network solution built for online games. Rapidly enables full-scale multiplayer games or online solo adventures.
    • Why open source? Is there a truly open source server backend for connected games? There is now. Download and run a local copy of Namazu Elements and try it for yourself.
    Download Namazu Elements

    Get started

    • Quick start Read our Elements 5-minute quick start guide
    • Documentation Read our developer docs for learning more about Elements
    • RESTful APIs A full list of core API specs for working with the Elements framework
    • Security An overview of the server-authoritative security model of Elements
    • Accessing the CMS Manage your game with ease via the Namazu Elements CMS.

    Co-development Reimagined

    • Best real-time game backends in 2026 If you're researching an alternative to your current backend solution, we've prepared a report of all of the backend solutions on the market in 2026 and how Namazu Elements compares.
      Co-dev

    Recent Posts

    • The watercolor-styled Namazu Studios logo over a giant namazu lurking in the depth
      Namazu Studios Featured in San Diego Business Journal
      22 Sep 2025 Press
    • Namazu Elements 3.1 Released – Service Layer Fixes, Secure APIs, and Steam Bug Fix
      22 Apr 2025 Release Notes
  • Case Studies
  • About Us
  • News
  • Services
  • Book a call
namazu-studios-logo
Book a call
Popular Search Roblox

Getting Started

  • Namazu Elements in Five Minutes or Less
  • Overview
  • Accessing the Web UI (CMS)
  • CMS Feature Overview

Fundamentals

  • Why You Need a Server (and What “Authoritative” Means)
  • Elements as a Game Runtime
  • Where Your Authoritative Code Runs
  • Lifecycles and Flows

General Concepts

  • Custom Elements
  • Data Models
  • Security Model
  • N-Tier Architecture

Namazu Elements Core Features

  • Email Service
  • Applications
  • Sessions
  • Users and Profiles
  • Digital Goods
  • Progress and Missions
  • Progress and Missions (3.4+)
  • Leaderboards
  • Matchmaking – Comprehensive Guide
  • Friends
  • Followers
  • Product Bundles and SKUs
  • Item Ledger
  • Receipts
  • Reward Issuances
  • Save Data
  • Metadata
  • Metadata (3.4+)
  • Queries
  • User Authentication / Sign In
    • What is a User?
    • Email Verification
    • User Authentication in Elements
    • Account Linking
    • Setting Up Twitch OIDC Login (Backend)
    • OIDC Login for Thick Clients (Browser Redirect Flow)
    • Auth Schemes
      • Auth Schemes
      • OAuth2
      • OIDC
  • Features
    • Web3
      • Wallets
      • Vaults
      • Omni Chain Support
      • Smart Contracts
        • Smart Contracts
  • Queries
    • Advanced Operators
    • Object Graph Navigation
    • Boolean Queries
    • Base Query Syntax
  • Advanced Operators
    • .name
    • .ref

Your Game Code - Adding Custom Elements

  • Custom Code Overview
  • Windows Setup
  • Mac OS Setup
  • Ubuntu Linux Setup
  • Element Anatomy: A Technical Deep Dive
  • Introduction to Guice and Jakarta in Elements
  • Structuring your Element
  • Events
  • Packaging an Element with Maven
  • Deploying an Element
  • Preparing for code generation
  • Properties
  • Websockets
  • RESTful APIs
  • Direct MongoDB Access (3.5+)
  • Building the Example Element: A Complete Walkthrough
  • Building the Kotlin Example Element: A Complete Walkthrough

Configuration

  • Configuring External URLs for Deployment
  • Matchmaking – Comprehensive Guide
  • Direct Database Access and Batch Configuration
  • Connecting Namazu Elements to a TLS-Enabled MongoDB Replica Set
  • Batch Samples
    • Mission Upload Bash Script Sample
    • Item Upload Bash Script Sample

RESTful APIs

  • Importing into Postman
  • RESTful APIs Library
  • Swagger and Swagger UI

Add-Ons

  • Crossplay
    • Crossfire Client Libraries (JVM & Browser)
    • Crossfire Protocol Reference
    • Crossfire: Custom Matchmaking Algorithms
    • Namazu Crossfire (Multiplayer)
    • Deploying Namazu Crossfire in your game
  • Roblox
    • Roblox Overview
    • Secure Player Authentication & Registration
    • Global Matchmaking
    • Roblox Security Best Practices
  • Container on Demand
    • Namazu Conductor
    • Namazu Conductor Admin API
    • Configuring Namazu Conductor Providers
  • Commerce
    • Stripe
      • Stripe
      • Configuring the Stripe Element
      • Stripe REST API Reference
      • Stripe REST API Reference

Game Engine & Client Support

  • Unity
    • Elements Unity Plugin
    • Unity Crossfire Plugin
  • Gamemaker
    • Incorporating GMEXT-Elements into a GameMaker Project

Troubleshooting

  • Common Issues with Docker
  • Local SDK
    • Unable to deploy application : dev.getelements.elements.sdk.exception.SdkElementNotFoundException
    • Could not load class : java.lang.NoClassDefFoundError
  • Namazu Elements Community Edition
    • Common Issues with Docker
    • Unable to deploy application : dev.getelements.elements.sdk.exception.SdkElementNotFoundException
    • Running in the IDE
      • Exception in monitor thread while connecting to server localhost:27017
      • Could not deployAvailableApplications Jetty server Failed to bind to /0.0.0.0:8080 Address already in use

Releases

  • 3.8 Release Notes
  • 3.7 Release Notes
  • 3.6 Release Notes
  • 3.5 Release Notes
  • 3.4 Release Notes
  • 3.3 Release Notes
  • 3.2 Release Notes
  • 3.1 Release Notes
View Categories
  • Home
  • Docs
  • Add-Ons
  • Commerce
  • Stripe
  • Stripe REST API Reference

Stripe REST API Reference

Est. read time: 5 min read

AI Doc Summarizer Doc Summary
AI Doc Summarizer Thinking Thinking

This page documents every REST endpoint exposed by the Stripe Element. All paths are relative to the configured RS root, dev.getelements.elements.Element.rs.root (default /Element/stripe/api) — so /stripe/payment-intent below means /Element/stripe/api/stripe/payment-intent on a default deployment. Every endpoint except the webhook receiver requires the session_secret security scheme. The full OpenAPI document is served at /api/REST/openapi.json once the Element is running.


Webhook #

MethodPathAuthDescription
POST/stripe/webhookNone (signature-verified)Receives and verifies a Stripe webhook, then publishes typed and raw internal events. See Stripe Webhooks and the Typed Event Bus.

Customers #

MethodPathRequestResponseDescription
PATCH/stripe/customer/{customerId}UpdateCustomerRequest204 No ContentUpdates a customer’s email and/or display name. null fields are left unchanged.
GET/stripe/customers/search?key=&value=—CreateCustomerResponseFinds a customer by a Metadata key/value pair. Returns 404 if none match. Use key=orgId for find-or-create.
POST/stripe/customer/{customerId}/portal-Session?returnUrl=—CreatePortalSessionResponseCreates a single-use Stripe Customer Portal Session URL.

UpdateCustomerRequest(String email, String name). CreateCustomerResponse(String customerId). CreatePortalSessionResponse(String url).


Payments #

MethodPathRequestResponseDescription
POST/stripe/payment-intentCreatePaymentIntentRequestCreatePaymentIntentResponseCreates a PaymentIntent for a one-off charge and returns its client secret.

CreatePaymentIntentRequest(long amount, String currency, String customerId, String description, Map<String,String> Metadata, Boolean automaticPaymentMethods, String setupFutureUsage, String idempotencyKey) — amount is in the currency’s smallest unit (e.g. cents); customerId may be null for guest checkouts; setupFutureUsage set to "off_session" saves the payment method for later charges. CreatePaymentIntentResponse(String paymentIntentId, String clientSecret).


Subscriptions #

MethodPathRequestResponseDescription
POST/stripe/customer/{customerId}/subscriptionCreateSubscriptionRequestSubscriptionStatusResponseCreates a recurring subscription. The customer must already have a default payment method on file.
GET/stripe/subscription/{subscriptionId}—SubscriptionStatusResponseGets the current status of a subscription.
DELETE/stripe/subscription/{subscriptionId}—SubscriptionStatusResponseImmediately cancels a subscription; the customer loses access at once. Returned status is canceled.
GET/stripe/customer/{customerId}/subscriptions?status=&limit=10&startingAfter=—SubscriptionListResponseLists subscriptions for a customer, newest first. status is a Stripe status filter (e.g. active, canceled, all); omitted uses Stripe’s default of non-canceled only.

CreateSubscriptionRequest(String priceId, String description, Map<String,String> Metadata, String idempotencyKey) — factory of(priceId) covers the common case. SubscriptionStatusResponse(String subscriptionId, String status, String currentPeriodEnd). SubscriptionListResponse(List<SubscriptionStatusResponse> subscriptions, boolean hasMore, String nextCursor) — pass nextCursor back as startingAfter to page.


Checkout and Invoices #

MethodPathRequestResponseDescription
POST/stripe/checkout-SessionCreateCheckoutSessionRequestCreateCheckoutSessionResponseCreates a Stripe-hosted Checkout Session and returns its URL.
GET/stripe/customer/{customerId}/invoices?limit=10&startingAfter=—List<InvoiceSummary>Lists invoices for a customer, newest first, with cursor pagination.

CreateCheckoutSessionRequest(String customerId, String priceId, String successUrl, String cancelUrl, String mode, String idempotencyKey, Map<String,String> Metadata) — mode defaults to subscription if null; use payment for a one-off charge. CreateCheckoutSessionResponse(String sessionId, String url). InvoiceSummary(String id, String subscriptionId, Long amountPaid, String currency, String status, String createdAt) — status is one of draft, open, paid, uncollectible, void.


Catalogue: Products and Prices #

MethodPathResponseDescription
GET/stripe/products?active=true&limit=100List<ProductSummary>Lists products from the Stripe catalogue.
GET/stripe/prices?productId=&active=true&limit=100List<PriceSummary>Lists prices, optionally filtered by product. Cached in memory (TTL: dev.getelements.elements.stripe.price.cache.ttl.ms).
GET/stripe/prices/{priceId}PriceSummaryRetrieves a single price by id directly, without needing its product id.

ProductSummary(String id, String name, String description, boolean active, PriceSummary defaultPrice) — active: false means archived. PriceSummary(String id, String productId, String nickname, Long unitAmount, String currency, String type, String interval) — unitAmount is null for usage-based prices; type is one_time or recurring; interval is day, week, month, or year for recurring prices, otherwise null.


Billing Meters #

MethodPathRequestResponseDescription
POST/stripe/meter-eventRecordMeterEventRequest204 No ContentReports a usage event to a Stripe Billing Meter. Throws NoSuchMeterException (surfaced as an error response) if Stripe has no active meter for the given event name.

RecordMeterEventRequest(String customerId, String eventName, BigDecimal value, String idempotencyKey) — value must be greater than zero; a long-value convenience constructor exists for whole-unit usage. The idempotencyKey is used both as Stripe’s own meter-event deduplication identifier and as the HTTP idempotency key, so retrying with the same key never double-reports usage.

Note

listMeters and both overloads of resolvePriceForMeterEventName — the meter-to-price join described in Stripe → Products, Prices, and Billing Meters — are StripeService methods only. There is no REST endpoint for them; call them from an Element that depends on the Stripe api module.


Configuration and Event Log (Superuser) #

MethodPathRequestResponseDescription
GET/stripe/config—StripeConfigReturns the effective Stripe credentials with values masked (e.g. ••••1234).
PUT/stripe/configStripeConfig{"saved":true}Persists Stripe credentials to the database, overriding the deployment’s attributes.
GET/stripe/events?type=&limit=20&offset=0—StripeEventLogResponseLists received webhook events, newest first, with type filtering and offset pagination.

StripeConfig(String apiKey, String webhookSecret). StripeEventLogResponse(List<StripeEventLogEntry> events, long total, boolean hasMore), where StripeEventLogEntry(String stripeEventId, String eventType, String receivedAt). See Configuring the Stripe Element for credential precedence.


Service-Only Methods #

Not every StripeService capability is exposed over REST. The following are reachable only by injecting StripeService from another Element that depends on Stripe’s api module — there is deliberately no HTTP surface for them, either because they’re building blocks for server-side flows (customer/payment-method setup ahead of a charge) or because they’re only meaningful to trusted server code (recording a receipt from inside the webhook handler):

  • createCustomer(email, name, orgId)
  • createSetupIntent(customerId)
  • listPaymentMethods(customerId) / hasPaymentMethod(customerId)
  • getProduct(productId)
  • listMeters(activeOnly, limit)
  • resolvePriceForMeterEventName(eventName) and resolvePriceForMeterEventName(eventName, subscriptionId)
  • recordPaymentReceipt(transactionId, amount, currency, userId) — called internally by the webhook handler; not intended to be called from arbitrary server code

Related Pages #

  • Stripe — Element overview and core concepts
  • Configuring the Stripe Element — attributes and credential precedence
  • Stripe Webhooks and the Typed Event Bus — the webhook endpoint and typed events in detail
What are your Feelings
Still stuck? How can we help?

How can we help?

Updated on August 14, 2026
Configuring the Stripe ElementStripe REST API Reference
Table of Contents
  • Webhook
  • Customers
  • Payments
  • Subscriptions
  • Checkout and Invoices
  • Catalogue: Products and Prices
  • Billing Meters
  • Configuration and Event Log (Superuser)
  • Service-Only Methods
  • Related Pages
  • Documentation
  • Terms of Service
  • Privacy Policy
  • Contact us
  • Linkedin
  • Join our Discord

Namazu Studios LLC is powered by Namazu Elements, an open source modular backend framework for connected games.

Namazu Elements
  • Download
  • About Elements
  • Open source
  • Documentation
  • Support
Namazu Studios
  • Case Studies
  • About Us
  • News
Best realtime game backends 2026
Get in Touch
  • info@namazustudios.com
  • Book a call
  • (619) 862-2890
  • Linkedin
  • Discord

©2008-2026 Namazu Studios. All Rights Reserved.