Stripe Setup

Configure the Stripe integration to sell licenses directly through Stripe Checkout Sessions, with full support for subscriptions and one-time payments.

Settings

Navigate to LicenceForge > Settings > Stripe to configure the integration. The following settings are available:

API Key Encryption

All Stripe API keys are encrypted before being stored in the WordPress options table using WPLF_Crypto::encrypt_option(). This ensures that sensitive credentials are never stored in plain text in the database.

// Keys are encrypted before storage
WPLF_Crypto::encrypt_option( 'wplf_stripe_test_secret_key', $test_key );
WPLF_Crypto::encrypt_option( 'wplf_stripe_live_secret_key', $live_key );

// Keys are decrypted on retrieval
$secret_key = WPLF_Crypto::decrypt_option( 'wplf_stripe_' . $mode . '_secret_key' );

Configuration Check

LicenceForge provides an is_configured() method to verify that the Stripe integration is ready for use. This method checks whether an API key is present for the current mode.

// Check if Stripe is configured
if ( WPLF_Stripe_Service::is_configured() ) {
    // Stripe is ready to accept payments
}

// Internally, is_configured() checks:
// - stripe_mode is set to 'test' or 'live'
// - The corresponding secret key is present and decryptable

API Requests

All Stripe API calls are routed through the WPLF_Stripe_Service::request() method. This central method handles:

• Automatic selection of the correct API key based on the current mode (test/live)
• Request signing and authentication
• Error handling and response parsing
• Logging of API calls for debugging

// All API calls go through the central request method
$response = WPLF_Stripe_Service::request( 'POST', '/v1/checkout/sessions', [
    'mode'        => 'subscription',
    'line_items'  => [ /* ... */ ],
    'success_url' => $success_url,
    'cancel_url'  => $cancel_url,
] );

Checkout Sessions

LicenceForge creates Stripe Checkout Sessions via create_checkout_session(). The session mode depends on the price tier's billing interval:

Session metadata

LicenceForge attaches metadata to each Checkout Session so that webhook handlers can create the correct license when the session completes:

// Creating a checkout session
$session = WPLF_Stripe_Service::create_checkout_session( [
    'price_tier' => $price_tier,
    'success_url' => home_url( '/checkout/success/?session_id={CHECKOUT_SESSION_ID}' ),
    'cancel_url'  => home_url( '/checkout/cancel/' ),
] );

// Internally builds:
// mode     => 'subscription' (for month/year) or 'payment' (for lifetime)
// metadata => [ 'product_slug', 'price_id', 'activation_limit' ]

Setup Steps

1. Log in to the Stripe Dashboard.
2. Copy your Secret Key from Developers > API keys (test and/or live).
3. In WordPress, go to LicenceForge > Settings > Stripe.
4. Select your Mode (test or live).
5. Paste the corresponding Secret Key.
6. Set up a webhook endpoint in Stripe (see Stripe Webhooks).
7. Paste the Webhook Signing Secret into the LicenceForge settings.
8. Save settings and run a test purchase.