38.1 Payment Settings Overview

AIUNIFY Funnels supports user-level payment configuration for PayPal and Stripe through the Payment Settings area of Account Settings.

These credentials are used by the supported Landing Page Ecommerce checkout workflow.

38.2 Opening Payment Settings

1. Sign in to AIUNIFY Funnels.
2. Open Account Settings.
3. Open Payment Settings when that tab is available to your account.

The application conditionally includes this payment configuration when Ecommerce account-payment functionality is available.

38.3 PayPal Settings

The PayPal section states that customers can pay using their PayPal account or a supported major credit or debit card.

The confirmed PayPal settings are:

Environment	Selects the PayPal operating environment.
Sandbox	Uses PayPal's test environment.
Live	Uses the live PayPal environment for real transactions.
Client ID	Stores the PayPal client identifier used by the integration.
Secret	Stores the PayPal secret credential used by the integration.

38.4 PayPal Environment

The saved PayPal environment is passed to the payment library as its test-mode setting.

Use Sandbox while testing with PayPal sandbox credentials. Use Live only when you are intentionally ready to process real transactions with valid live credentials.

38.5 PayPal Client ID and Secret Must Work Together

The Landing Page checkout workflow checks for both:

1. PAYPAL_CLIENT_ID
2. PAYPAL_SECRET

If the required PayPal configuration is missing, checkout can return:

You need config setting payment PayPal in account setting

38.6 PayPal Merchant Branding

The confirmed PayPal gateway initialization uses the AIUNIFY Funnels user's name as the PayPal integration brand name.

Review your PayPal merchant account separately to ensure its customer-facing business information is also configured correctly.

38.7 Stripe Settings

The Stripe section states that customers can pay using supported major credit or debit cards.

The confirmed Stripe settings are:

Publishable key	Stores the Stripe publishable credential. The interface uses a pk_XXX style placeholder.
Secret key	Stores the Stripe server-side secret credential used to create and retrieve supported Stripe Checkout sessions.

38.8 Stripe Keys Must Work Together

The Landing Page checkout workflow checks for both:

1. STRIPE_KEY
2. STRIPE_SECRET

If the required Stripe configuration is missing, checkout can return:

You need config setting payment STRIPE in account setting

38.9 How Stripe Uses the Secret Key

Before creating a Stripe Checkout Session, AIUNIFY Funnels configures the Stripe API using the saved Stripe Secret key.

The Checkout Session then uses the Order's:

1. Product Name.
2. Total.
3. Currency.

38.10 Stripe Checkout Is a One-Time Payment Workflow

The confirmed Stripe Checkout Session uses:

mode = payment

This Ecommerce workflow therefore represents the application's supported one-time Landing Page Product checkout rather than a recurring Stripe subscription workflow.

38.11 Protect Secret Credentials

PayPal Secret and Stripe Secret key values are sensitive merchant credentials.

Never place these values in:

1. Landing Page text.
2. Form fields.
3. Custom Header or Footer code.
4. Public messages.
5. Customer-facing documentation.

38.12 Do Not Mix Sandbox and Live Credentials

A common payment-configuration error is combining credentials from different environments.

For PayPal, make sure the Environment corresponds to the credentials entered.

For Stripe, make sure the Publishable and Secret keys belong to the same intended test or live environment within your Stripe account.

38.13 Payment Settings Are Account-Level

The payment gateways read the Landing Page owner's saved account settings during checkout.

This means payment credentials are not configured separately inside every Product record.

38.14 Landing Page Payment-Success Behavior Is Configured Separately

Payment credentials determine how the supported payment is processed.

The visitor's destination after a successful payment is controlled separately by the Landing Page's payment-success configuration documented in Chapter 30.

A successful payment can direct the visitor either to:

1. The configured payment Redirect URL.
2. The Landing Page Thank You Page.

38.15 Changing Merchant Credentials

If you replace PayPal or Stripe credentials, test a supported Landing Page checkout again.

Do not assume that saving new credentials alone proves that:

1. The credentials are valid.
2. The environment is correct.
3. The currency is supported.
4. The customer return flow works.
5. The resulting Order will be marked Paid after gateway confirmation.

38.16 Recommended PayPal Setup Workflow

1. Obtain the appropriate PayPal merchant credentials.
2. Open Account Settings → Payment Settings.
3. Select Sandbox while testing or Live when intentionally launching real payments.
4. Enter the correct Client ID.
5. Enter the corresponding Secret.
6. Save the Account Settings.
7. Use a controlled Landing Page checkout to verify the connection.
8. Confirm the resulting Order.

38.17 Recommended Stripe Setup Workflow

1. Obtain the appropriate Stripe keys.
2. Open Account Settings → Payment Settings.
3. Enter the Publishable key.
4. Enter the matching Secret key.
5. Save the Account Settings.
6. Perform a controlled Stripe Checkout test.
7. Complete the payment flow.
8. Confirm the Order becomes Paid after successful gateway confirmation.
9. Confirm the correct payment-success destination.

Operating principle: Merchant credentials, Product information, and Landing Page payment-success settings are separate parts of one checkout journey. Configure and test all three before accepting live payments.