Payment management

View all customer transactions, inspect payment details, process refunds, and more in the Support Tool of your FunnelFox Billing dashboard.

View payments

You can view all the latest payments in your organization as well as all payments for a specific customer:

Go to the Support Tool page of your FunnelFox Billing dashboard. The latest payments appear below.
Search for a user or click the user UUID under Latest payments.

Click any transaction to view payment details.

This section includes all subscription payments, as well as one-offs.

Payment details

When you open a payment, you see the following details:

order ID — Unique identifier for this transaction.
payment method — Card details including masked number, expiration date, card type, and country.
amount — Total amount charged to the customer.
Price Point — The product and price purchased with pp_ident.
pop_payment_id — Internal payment identifier.
is_cit — Indicates if this is a Customer Initiated Transaction (CIT).
meta — JSON object containing payment context like iteration number, subscription ID, and payment type.

If you click Show Transactions in the payment details, you also see:

PSP transaction ID — Payment processor’s unique transaction identifier with status (authorized, settled, etc.).
PSP merchant ID — Merchant account identifier used for this transaction.
Amount — Transaction amount and type.
Transaction Date — When the PSP processed this transaction.
Created at — When FunnelFox Billing recorded this transaction.

A single order may have multiple PSP transactions as it moves through authorization and settlement stages.

Payment types

FunnelFox Billing handles two primary payment types: recurring subscription payments and one-off purchases.

Subscription payments

All your subscription payments appear under the Payments section.

Purchased subscriptions are displayed under Subscriptions. All payments are linked to active subscriptions and show the billing iteration in the metadata.

The Subscription engine API enforces a limit of two charges per day per payment method token.

One-off purchases

One-offs grant lifetime access. All transactions also appear under the Payments section along with subscription payments. Purchased one-offs are displayed under OneOff below.

Each purchased one-off shows:

OneOff ID — Unique identifier for the lifetime access grant.
Started At — When lifetime access was activated.
Revoked At — Shows “Not revoked” unless a full refund was issued.
Initial Order ID — Links to the original payment transaction.
Price Point — The lifetime product purchased and its price.

One-off purchases remain active permanently unless revoked through a full refund.

Free trials

You can launch free trials without payment transactions. When you create a price point with a free trial, FunnelFox Billing processes it like a normal payment but cancels it before completing the transaction. This saves payment details for subscription renewal without charging the customer.

Manage payments

FunnelFox Billing allows you to refund any payment or process one-click purchases (like upsells) using securely stored payment credentials.

Refunds

To ensure refunds are processed correctly, initiate them only through the Support Tool, Primer, or the FunnelFox Billing API. To process a refund in the Support Tool:

Open any payment while viewing payments for a specific customer.
Configure your refund:

Amount:
- If the entire amount is refunded (full refund), the subscription immediately becomes EXPIRED and the one-off payment is revoked.
- If a partial amount is refunded, auto-renewal is disabled automatically.
Soft refund: Refunds the payment but keeps auto-renewal enabled. The subscription or one-off remains active.

Optionally, provide additional information:

Reason — Reason code for the refund.
Comment — Custom message.

Click Refund.

Refunds are limited to 50 attempts per day per organization, and this limit is configurable per merchant.

One-click payment

Once a customer completes a purchase, their payment credentials are securely stored. This allows one-click payments for both one-off and subscription upsells without re-entering details. You can perform one-click payments from the Support Tool or using the FunnelFox Billing API.

One-click payments do not use a payment method token, so the two-charge limit per day does not apply.

To process a one-click payment in the Support Tool:

Find the customer on the Support Tool page.
Select the price point to upsell under the OneClick section.
Click Buy.

Payment method update

Customers may experience failed payment attempts due to issues with their payment method. FunnelFox Billing lets you redirect customers to the Update payment method page where they can provide a valid payment method. To activate this feature, contact your Solution manager.

Delayed capture

Authorize a payment immediately but delay the capture, giving your team a fraud review window before funds are settled by your . The order stays in authorized status until FunnelFox Billing captures it and moves it to settled. A cancellation before capture costs nothing, while a capture followed by a refund is a real money movement. and payments use separate delay settings.

Purchases, subscriptions, and outbound webhooks fire at authorization, not at capture. Customers get access immediately, and only the money settles later.

To enable payment hold:

Configure the delayed_capture on the Settings page of your FunnelFox Billing dashboard. The delay is , and a change . delayed_capture is a JSON field. Paste the whole matrix into it and click Save.

Delay capture JSON reference

{
    "networks": {
    "visa": {
    "cit": { "stripe": 12, "adyen": 24 },
    "mit": { "stripe": 12, "adyen": 24 }
},
    "mastercard": {
    "cit": { "stripe": 12, "adyen": 24 },
    "mit": { "stripe": 12, "adyen": 24 }
}
},
    "fallback": { "cit": 12, "mit": 12 }
}

Level	Allowed keys
Network	`visa`, `mastercard`. Any other network is rejected.
Transaction type	`cit`, `mit`
PSP	`stripe`, `braintree`, `paypal`, `adyen`, `checkout`, `primer_processor`, `airwallex`, `unlimint`
Delay	Hours, a number of 0 or more. Fractions such as `1.5` are allowed.
`fallback.cit`, `fallback.mit`	Hours of 0 or more, or `null`

There is no partial fall-through inside the JSON. A Visa CIT entry that does not list your PSP goes straight to the cit fallback.A null fallback captures on the next run. To turn the hold off everywhere, set {"networks": {}, "fallback": {"cit": null, "mit": null}}.A fallback that sets only cit leaves mit as null, so renewals capture immediately. Always write both keys.An authorization expires if it is held too long, so every delay is capped. FunnelFox Billing rejects a value above its cap when you save.

PSP	Visa CIT	Visa MIT	Mastercard CIT	Mastercard MIT
Stripe	89	89	89	89
Airwallex	96	96	96	96
Adyen	144	96	144	144
Unlimint	72	72	72	72
Braintree	47	47	47	47
PayPal, Checkout, Primer processor	216	96	144	144

Both fallbacks are capped at 47 hours. An order with an unknown network or PSP could be on the strictest acquirer, so the tightest cap applies.

Go to the Workflows page in your Primer dashboard.
Open your workflow.

Click Edit workflow at the top right.

Select the Authorize payment stage and set Before processing the next workflow block to Continue payment flow.

Click Save.

A capture is attempted at most twice, after which the payment is blocked for 12 hours. Orders older than 480 hours (20 days) are no longer picked up and the authorization is treated as dead. You can also capture an authorized order manually at any time, which ignores the configured delay.

Metadata

FunnelFox Billing attaches metadata to every payment request sent to Primer:

{
  "email": "user@example.com",
  "ff_adyen_shop_id_default": "ecom_00000_sub_merchant",
  "ff_country_code": "XX",
  "ff_initiation_type": "cit",
  "ff_org_id": "org_redacted",
  "ff_price_point": "price_redacted",
  "funnelfox": true,
  "ip_address": "ip_redacted",
  "postal_code": "00000",
  "test_client_metadata": "redacted",
  "user_agent": "Mozilla/5.0 ..."
}

By default, FunnelFox Billing includes the customer’s email in the metadata. If the email entered is not valid, it is skipped automatically. An email is valid only if it passes all of the following validation rules:

Must be a properly formatted email address (has a local part, an @ sign, and a valid domain).
Reject if the email ends with example@example.com.
Reject if the email starts with FIXME@.

You can also disable sending email in metadata entirely:

Go to the Settings page of your FunnelFox Billing dashboard.
Set Include email into primer request to No and save your changes.

Billing descriptor

The billing descriptor is the short text FunnelFox Billing sends with a charge, which the bank prints next to the amount on your customer’s card statement. It is also the label shown in the Apple Pay recurring payment sheet. Use a name customers recognize, such as your app or brand rather than your legal entity, for example ACME.COM. A recognizable descriptor reduces disputes opened for unrecognized charges. You can set the descriptor in two places:

Organization default: The statement descriptor setting applies to every price point that has no descriptor of its own.
Price point: The Descriptor field overrides the organization default for that price point.

Where you change the descriptor decides who sees the new text:

Where you change it	New purchases	Renewals of existing subscriptions
Organization default in Settings	Applies immediately to price points without their own descriptor	Applies immediately
Price point Descriptor	Applies immediately	No change. Renewals keep the descriptor the price point carried when it was sold

A descriptor accepts up to 22 characters: letters, digits, spaces, and . , _ ? + / -. Other characters, including apostrophes and &, are rejected and block saving. Once set, FunnelFox Billing sends the descriptor to Primer and to Stripe, where it is the suffix appended to your Stripe account’s own prefix. Adyen, PayPal, Braintree, Checkout.com, and Airwallex take statement text from their own account configuration, so set it there.

Saving a price point with an empty Descriptor stores the current organization default into that price point, so it no longer follows later changes to the default. A price point stays genuinely empty only if it was saved while the organization default was also empty.

Email

When a customer purchases a subscription, FunnelFox Billing stores their email if it was collected in the funnel. To view it:

Find the customer through the Support Tool page.
The email appears under the User Information section.

You can also collect email automatically from Apple Pay at checkout, without requiring a manual input in the funnel:

Go to the Settings page of your FunnelFox Billing dashboard.
Set collect_apple_pay_email to Yes and save your changes.

Learn how to update customer emails stored in FunnelFox Billing.

Once enabled:

If email is collected both from a funnel input and from Apple Pay, the Apple Pay email takes priority.
The system keeps both addresses: the secondary email is stored as an alias.
When an Apple Pay email is captured, a user webhook fires with the update_email subtype.
The Apple Pay email is not included in payment metadata. It is available directly in FunnelFox Billing.

This ensures you always have a valid email for your customers, even if they enter a placeholder email in the funnel.

Getting started

Payments

Subscription management

Settings

Payment management