Connect Alternative Payments

Alternative Payments is a payments and accounts-receivable platform built for MSPs. You create customers and invoices in it (or sync them from your PSA or accounting system), your customers pay by…

Written By Christopher Scaminaci

Last updated About 3 hours ago

Alternative Payments is a payments and accounts-receivable platform built for MSPs. You create customers and invoices in it (or sync them from your PSA or accounting system), your customers pay by card or ACH through hosted pages or Autopay, and Alternative Payments pays the money out to you.

Connecting Alternative Payments to StackJack gives your AI assistant a family of altpay_ MCP tools. MCP (Model Context Protocol) tools are the standardized commands an AI assistant can call through StackJack. With them, your AI can:

Look up customers - companies, their portal users and the payment methods they have saved
Follow the money - invoices and their status, payments, refunds, and the payouts that settle to your bank, with each payout's transactions
Collect (on Pro plans) - create invoices, charge a customer's saved card or bank account, send a hosted payment link, and refund a payment
Keep the books in step - attach the original PDF to an invoice synced from your accounting system, and read or manage your webhook subscriptions and the events behind them
Run a hosted checkout - the payer-side calls a checkout page makes, driven for you with a one-hour token that StackJack mints and never shows
Analyze receivables and cash - aging, collection rates, fees, payout reconciliation and more, computed from your own payment data (Pro; the tools say how much data they read and answer with nothing rather than a guess when the data does not support a number)

How StackJack authenticates to Alternative Payments

Alternative Payments does not use a sign-in screen for integrations. You generate an API key in the Partner Dashboard, which gives you a Client ID and a Client Secret. StackJack exchanges the pair with Alternative Payments for an access token that lasts an hour, sends that token on every call and renews it by itself. You never see the token.

The connection belongs to your organization in StackJack, not to one person, and one key serves your whole team.

Production and Demo are separate

Alternative Payments runs a Production service and a Demo service. They are separate worlds: a key generated in one does not work in the other, and an ID from one does not exist in the other. When you connect, you choose which one the key belongs to. A Demo connection is a safe place to try StackJack without touching real money.

Getting a Client ID and Client Secret

Sign in to the Alternative Payments Partner Dashboard (the Demo dashboard if you want a Demo key).
Go to Team Preferences, then API Keys, and click Generate API Key.
Name it "StackJack" so you can recognize it later.
Choose its scopes, as described below.
Copy the Client ID and the Client Secret and keep them safe.

The scopes you choose decide what the key can do

An API key's scopes are fixed when it is generated and cannot be changed afterwards. For read-only use and for every financial analysis tool, tick read on Customers, Invoices, Payments, Payouts, Refunds and Webhooks. Add write scopes only for what you want your AI to do:

Invoices write to create, archive and restore invoices and to attach PDFs
Payments write to charge saved methods, add or remove payment methods and create payment requests
Refunds write to refund
Customers write to create, change, archive and restore customers and their portal users
Webhooks write to manage subscriptions
Checkout write for the hosted-checkout tools

Select all gives full access. A key that lacks a scope still connects; a tool that needs the missing scope answers with a refusal that names the scope to add, and you fix it by generating a new key with the scope ticked. Nothing about the key itself is wrong in that case.

Connect it in StackJack

Open the Connectors page and choose Alternative Payments.
Choose the Environment: Production, or Demo for a Demo key.
Paste the Client ID and the Client Secret.
Save, then use Test Connection.

Enter the Client ID and Client Secret together each time you save. StackJack stores them encrypted and never shows them again. If you ever need to move a connection between Production and Demo, enter the key for the new environment, because keys do not cross.

What is worth knowing before you start

Charges and refunds move real money, and need an idempotency key

Charging a customer, refunding a payment and paying an invoice through the checkout lane are the three calls that move money. Each one needs an idempotency key: a UUID that you make once per intended charge and reuse unchanged if you retry. Alternative Payments uses it so that a retry can never charge the same payment twice. StackJack never retries a charge or a refund by itself, so if a call times out, your AI looks the payment up first and, if it must retry, sends the same key again.

Charges, refunds, new invoices, archiving an invoice, restoring an invoice, archiving a customer and every change to a saved payment method are marked destructive, so your AI prompts for approval before running them.

Amounts are US dollars, with two decimal places

Every amount is a US dollar figure with at most two decimal places, such as 49.99, never cents. StackJack refuses an amount with more precision rather than rounding it, and refuses a zero or negative amount before anything is sent. Invoices are issued in US dollars only.

Webhook events are the exception: the amounts inside a webhook payload are in cents, which is a different unit from the API. The tools that list webhook events say so.

"sub_total" means three different things

On an invoice, total is the face value and sub_total is what is still outstanding. On a payment or a refund, total is the gross and sub_total is the net after fees. On a payout, total is the gross and sub_total is the net after fees. The tool descriptions repeat this where it matters.

Lists come back in pages, with no total

List tools return up to 100 rows at a time, and Alternative Payments does not say how many exist in all. Each answer carries has_next_page and end_cursor; your AI passes the end_cursor back as after to get the next page. StackJack caps a page at 100, a limit it chose because Alternative Payments documents none.

What the API does not tell you

Alternative Payments does not put the date an invoice was paid on the invoice, and it does not say which payment settled which invoice: a payment carries no invoice ID, although you can filter payments by invoice. Nothing about the tools hides this. Where a financial analysis tool needs a paid date it asks Alternative Payments for the payment behind each invoice, says that it sampled, and tells you how many invoices it could not match.

There are two other gaps worth knowing. A failed payment carries no reason, and there is no call that lists payment requests, so keep the ID a payment-request tool returned. Accounts Payable (vendors and bills) is mentioned in Alternative Payments' documentation but has no API calls yet, so StackJack has no Accounts Payable tools.

Cards cannot be typed in

Alternative Payments states that its Web SDK is the only supported way to collect card details: the card goes straight from the payer's browser to a secure vault, and your system only ever sees an encrypted token. So the card tools take that token and cannot take a card number. Bank accounts (ACH) can be saved directly, with the routing and account number, and those numbers go to Alternative Payments only: StackJack does not store or log them.

The hosted checkout tools make two requests per call

The thirteen altpay_checkout_ tools work on the payer's side of the API, using a one-hour token that is specific to one customer and one invoice. StackJack mints that token for you on every call, uses it for that one call and never returns it, which is why each of these tools takes a customer and an invoice. Your API key needs the Checkout write scope for this. One tool, altpay_create_checkout_token, hands you the token itself, for the rare case where you are building a checkout page of your own.

Attaching a PDF works only for synced invoices

Uploading the original PDF to an invoice (up to 10 MB, as base64 or as a public HTTPS link) works only for invoices that were synced from an accounting integration. An invoice created through StackJack or the API has no original document from your system, and Alternative Payments refuses the upload.

Webhook subscriptions

Your AI can create a subscription for any topic, including the Accounts Payable topics that Alternative Payments documents but does not yet list in its API schema. The shared secret you give is stored only by Alternative Payments, which shows its last four digits afterwards. Webhook subscriptions need an HTTPS address. Retrying failed webhooks resumes a paused delivery queue, so your endpoint may receive a burst of older events.

Plans and limits

Read tools are available on the Free tier. Everything that creates, changes, charges or deletes, and every financial analysis tool, is Pro. Business reaches the same tools as Pro and differs by monthly call quota.

Alternative Payments allows 5 requests per second per API key and answers 429 beyond that. StackJack paces its own requests below that limit and backs off when it is told to slow down.

See the generated Alternative Payments tool reference for the current inventory, plan assignment, input schemas, and destructive-action labels.

Financial analysis

The financial analysis tools (Pro) read your invoices, payments, refunds, payouts and customers and work out an answer for you. They do not pass Alternative Payments' own answer through: each one returns figures that StackJack computed, and it tells you what it computed from. Your API key needs read on the areas a tool reads (its description names them), and never a write scope.

How to read an analysis answer

Coverage. Every answer has a coverage block that says, for each list it read, how many records it analyzed, how many pages that took and whether it stopped early. A list is read to the end. If a list is longer than the tool's maxRecords limit (5,000 by default, 10,000 at most), the answer says truncated and the totals are lower bounds.
No guess. An average, rate, score or ratio that has nothing to be calculated from is null, never zero. A total of nothing is zero.
Units. Money is US dollars. Rates, shares and ratios are fractions (0.25 is 25 percent). Days are calendar days.
Invoices. "Invoiced" is the face value of an invoice. "Owed" is what is still outstanding. Archived invoices are never counted, and an invoice in the undefined RECEIVED status is shown apart as a payment in progress. Only succeeded card and ACH payments count as money collected.
Sampling. Alternative Payments does not say when an invoice was paid. Where a tool needs the paid date it looks up the payment behind a sample of paid invoices, one request each, spread fairly across your customers, and the answer says sampled, how many it checked and how it found the date. Alternative Payments allows 5 requests per second, so a sample of 500 takes about two minutes; every default is far smaller.
Heuristics. Where a figure is an estimate (a forecast, a recovery, a pairing of a refund with an invoice, a recurring-revenue estimate) the tool says so and states the rule it used.

The analysis tools

Tool	What it tells you	Defaults	Limits of the data
`altpay_ar_aging_report`	Who owes what and how late: the outstanding balance by days past due, per customer, and the balance-weighted average days past due	Today; buckets 30, 60, 90 days; top 25 customers	Invoice status is as of now, so a past date re-ages today's open invoices; an overdue invoice with no due date is listed as unaged
`altpay_cash_flow_forecast`	Expected collections week by week with a low and high bound, and the matching bank deposits	8 weeks; paid-date sample of 50; collection chances 97, 90, 75, 55 and 30 percent from current to 90+ days, lowered to a customer's own paid share where they have enough history	Cash in only: Alternative Payments has no payables to net off. It is an estimate and lists its assumptions
`altpay_collections_priority_list`	Whom to chase today: overdue invoices ranked by balance x lateness x risk, with the next action	Overdue by 1+ days; 25 invoices; no payment links	Payment-method risk is checked for the strongest candidates only. A payment link lets anyone who holds it view and pay the invoice
`altpay_dso_analysis`	Days sales outstanding by the count-back and simple methods, best-possible DSO and average days delinquent	6 months; count-back	A point-in-time reading: there is no DSO trend because Alternative Payments keeps no balance history. Null when the receivables are older than the window
`altpay_payout_reconciliation`	Whether each bank payout equals its transactions, and whether its fees add up	Last 30 days; 60 newest payouts	Needs one request per payout. Flags failed and empty payouts and failed, charged-back or refunded transactions. A payout whose total or net cannot be compared because an amount is missing is listed as unverified with the reason, never counted as reconciled
`altpay_payment_method_mix_and_fee_cost`	What each payment method costs: gross, net, fees you absorbed or passed on, plus a card-to-ACH what-if	Last 90 days; 25 percent of card volume moved	The what-if assumes customers would pay by ACH at today's ACH cost
`altpay_failed_payment_analysis`	Failure rates by method and customer, how much was recovered and the revenue still at risk	Last 90 days; 14-day recovery window	A failed payment carries no invoice or reason, so a recovery is a later success for the same customer and amount
`altpay_revenue_at_risk`	A 0 to 100 risk score per customer from overdue, failed payments, chargebacks, card problems and falling billing, and the monthly revenue behind the flagged ones	6 months; payment methods for 150 customers; flag at 25	Card signals are checked only for customers who owe money; the rest are not assumed fine
`altpay_customer_payment_behavior_scores`	A 0 to 100 score and A to F grade per customer from lateness, overdue balance, failed payments and chargebacks	Last 365 days; paid-date sample of 100	Sampled. A customer with fewer than 3 measured invoices is marked low confidence
`altpay_expiring_payment_methods`	Saved cards that have expired or expire soon, with what the customer owes and bills	Within 60 days; 150 customers	Customers are checked biggest debtor first; the rest are counted, not assumed fine. A card works through the last day of its expiry month
`altpay_cash_application_gaps`	Money missing between invoice and bank: payments no payout lists, payout transactions nobody owns, paid invoices with no payment	Last 30 days; 7 days to settle; sample of 100	A payment is matched to its payout by id. Manual payments are not checked. Pairing a refund with an invoice is a best guess
`altpay_monthly_close_pack`	The month-end numbers: invoiced, collected, refunds, chargebacks, fees, deposits, money in transit and receivables	One month you name	Receivables are those open now. The opening balance is approximate and only given for the current month
`altpay_period_over_period_trends`	Month, quarter or week series with change on the last period and on the same period a year earlier	12 months	A period that hit the record limit is marked incomplete. The current period is marked partial and carries no change figure
`altpay_recurring_revenue_estimate`	Estimated monthly recurring revenue, movements (new, expansion, contraction, churn), net and gross retention and ARR	13 months	Inferred from invoices because Alternative Payments has no subscription object. Retention needs 13 months
`altpay_customer_account_statement`	One customer's ledger, running balance, closing balance and aging	Last 365 days	The opening balance is approximate (Alternative Payments keeps no balance history) and is null if any list was cut short
`altpay_customer_financial_360`	An account-review pack for one customer: contacts, cards, lifetime billed and collected, a 12-month trend, failures, refunds, payouts and a behavior score	Paid-date sample of 50	Lifetime figures are lower bounds if a list was truncated
`altpay_anomaly_and_duplicate_detection`	Probable double billing and double charging, and unusually large invoices or payments	Last 90 days	The groups are candidates to review. An outlier needs six earlier records for that customer
`altpay_chargeback_and_refund_analysis`	Chargeback and refund ratios against a threshold	Last 180 days; threshold 0.0075 (0.75 percent)	The threshold is your own limit, not a card-network figure. Refund reasons are not returned
`altpay_fee_pass_through_analysis`	Who bears processing fees, and what passing card fees to customers would save	Last 90 days	The saving is an upper bound. Give a customer with a saved card to see the vendor's own fee split
`altpay_autopay_adoption_report`	Customers with and without a saved default payment method compared on how much is paid and overdue	Last 180 days	A saved default method stands in for Autopay, which Alternative Payments does not expose. It is a paid share, not an on-time share
`altpay_revenue_concentration`	How much of your invoicing comes from a few customers: top shares, concentration index, customers making up 80 percent	12 months; top 10	Measures who is invoiced, not who pays
`altpay_payout_forecast`	When cash reaches the bank, day by day	14 days	Payments are matched to payouts by id; the lag is measured from payouts in the last 30 days
`altpay_late_fee_and_interest_report`	Late-fee and interest income by month and customer, and repeat late payers	Last 365 days	Read from the fees on succeeded payments
`altpay_line_item_revenue_mix`	Which services earn the money, with a first-half against second-half trend	6 months; top 25	Descriptions are folded together by removing dates and numbers; tax or adjustments not on a line show as a gap
`altpay_cash_cycle_timeline`	Where cash waits: terms, customer delay, lateness against the due date, payout start and bank transfer	Last 180 days; sample of 100	Customer delay and payout start come from a sample; terms and bank transfer use every record. An invoice Alternative Payments returns without a created date is left out of customer delay and counted in the coverage block
`altpay_dunning_effectiveness`	Whether reminders work: how many reminded invoices were paid within 3, 7 and 14 days, and overdue invoices nobody has reminded	Last 180 days; sample of 100	Only the last reminder time is available, so the delay is measured from the final reminder
`altpay_webhook_delivery_health`	Whether your webhook feed is being delivered: failed and pending events and whether delivery looks paused	7 days	Counts events only. Webhook payloads carry cents, so nothing is added up

Alternative Payments does not expose accounts payable, a history of balances, refund reasons, dispute evidence or a list of payment requests, so none of the tools can answer questions that depend on them.

Several Alternative Payments accounts

If you hold more than one Alternative Payments account, or you want a Demo connection beside Production, add one connection per account from the connector's card, name it after the account, and your AI names it on each call. Omit the name and the call runs on the default connection.

Troubleshooting

"Test Connection" fails straight after saving. Check the Environment first. A Demo key sent to Production, or a Production key sent to Demo, is refused exactly like a wrong secret. Then check that the Client ID and Client Secret are both pasted in full.

Alternative Payments did not accept the API key. The key may have been revoked, deleted or replaced. In the Partner Dashboard, open Team Preferences, then API Keys, and check it is still listed. A revoked key is gone for good, so generate a new one, then open the connector in StackJack and enter the new Client ID and Client Secret.

A tool answers that the key does not have the scope it needs. The key is fine. In the Partner Dashboard, generate a new key with the scope the message names ticked (or use Select all), then update the connector in StackJack with the new Client ID and Client Secret. A key's scopes cannot be edited.

A tool answers "not found" for something you can see in the dashboard. Check that the connector's Environment matches the dashboard you are looking at, and that you are passing the ID exactly as a list tool returned it.

A charge or a refund is refused with a message about a rule. Alternative Payments answers 422 when it understands the request but a rule forbids it: a payment method that cannot be charged, an invoice that is already paid, an archived customer, or a card that needs its security code registered first. The message names the rule, and nothing was charged or changed.

A tool answers that Alternative Payments is rate limiting StackJack. Wait a moment and try again, and narrow a large sweep to a shorter date range or one customer at a time.

Alternative Payments tools

altpay_ · 85 tools · Free 33 · Pro 52

Customers

Tool	What it does
`altpay_address_autocomplete` Free · Read-only	Address suggestions for the text typed so far, from Google Places (a proxy the API offers).
`altpay_archive_customer` Pro · Destructive	Archive a customer (the vendor's DELETE).
`altpay_create_customer` Pro · Write	Create a customer (a company the partner bills).
`altpay_create_customer_user` Pro · Write	Create a portal user for a customer: it gives the person access to the customer-facing portal where they can pay invoices and manage payment methods.
`altpay_get_address_details` Free · Read-only	The full address (address components and name) for one place_id returned by altpay_address_autocomplete, from Google Places.
`altpay_get_customer` Free · Read-only	Get one customer by id: name, legal name, EIN, address, email, external_id, default_payment_method_id and the customer_integration_id when the customer was synced from a PSA or accounting integration.
`altpay_list_customer_users` Free · Read-only	List the portal users of one customer: the people who can sign in to the customer-facing payment portal to pay invoices.
`altpay_list_customers` Free · Read-only	List customers, newest first by the vendor's default order, with optional filters by creation date and company name.
`altpay_restore_customer` Pro · Write	Restore an archived customer (the reverse of altpay_archive_customer).
`altpay_update_customer` Pro · Write	Patch a customer's company details: name, legal name, EIN and address.

Payment methods

Tool	What it does
`altpay_calculate_card_fees` Free · Read-only	Calculate the fee split for charging an amount on a saved card: the percentage and fixed fee for the customer and for the partner.
`altpay_create_customer_bank_account` Pro · Destructive	Save a bank account (ACH) on a customer.
`altpay_create_customer_card` Pro · Destructive	Save a card on a customer from an Evervault card token.
`altpay_delete_customer_payment_method` Pro · Destructive	Delete a customer's saved payment method.
`altpay_get_card_form_credentials` Free · Read-only	The Evervault app_id and team_id the Alternative Payments card form needs: public identifiers for the secure card iframe, not secrets.
`altpay_get_customer_payment_method` Free · Read-only	Get one saved payment method of a customer by id: brand, last4, expiry, type (card or ach), whether it is the default.
`altpay_list_customer_payment_methods` Free · Read-only	List a customer's saved payment methods: cards (brand, last4, expiry) and bank accounts (type ach), with the default flagged.
`altpay_register_card_cvv` Pro · Write	Register an encrypted CVV token for a saved card and ONE invoice, ahead of charging that card for that invoice.
`altpay_set_default_payment_method` Pro · Destructive	Make a saved payment method the customer's default.

Invoices

Tool	What it does
`altpay_archive_invoice` Pro · Destructive	Archive an invoice (the vendor's DELETE).
`altpay_create_invoice` Pro · Destructive	Create an invoice for a customer from line items.
`altpay_get_invoice` Free · Read-only	Get one invoice by id, with its line items.
`altpay_get_invoice_payment_link` Free · Read-only	The hosted payment page URL for an invoice: send it to the payer to pay by card or ACH.
`altpay_get_invoice_pdf_link` Free · Read-only	A signed, time-limited URL to download an invoice's PDF.
`altpay_list_invoices` Free · Read-only	List invoices with optional filters by customer, status, invoice number, creation date and due date.
`altpay_restore_invoice` Pro · Destructive	Restore an archived invoice.
`altpay_upload_invoice_pdf` Pro · Write	Attach the original invoice PDF (10 MB maximum) to an invoice, replacing any earlier one.

Payments

Tool	What it does
`altpay_create_payment` Pro · Destructive	Charge a customer's saved card or bank account against an invoice.
`altpay_create_payment_request` Pro · Write	Create a standalone hosted payment request: a one-off pay link for an amount, with no invoice.
`altpay_get_payment` Free · Read-only	Get one payment by id: status, payment method, total (gross), sub_total (NET after fees) and each fee with who covered it.
`altpay_get_payment_request` Free · Read-only	Get a payment request and its current status.
`altpay_list_payments` Free · Read-only	List payments with optional filters by type (payment, refund, chargeback), status, payment method, customer, invoice and creation date.

Refunds

Tool	What it does
`altpay_create_refund` Pro · Destructive	Refund a payment IN FULL (the vendor does not support partial refunds).
`altpay_get_refund` Free · Read-only	Get one refund by id: payment method, total (gross), sub_total (NET after fees) and its fees.
`altpay_list_refunds` Free · Read-only	List refunds with optional filters by customer, invoice, payment method and creation date.

Payouts

Tool	What it does
`altpay_get_payout` Free · Read-only	Get one payout by id: status, arrival_date, total (gross), sub_total (NET after fees) and its fees.
`altpay_list_payout_transactions` Free · Read-only	The transactions that make up one payout (each with direction credit or debit, method, status, total and sub_total) together with the payout itself.
`altpay_list_payouts` Free · Read-only	List payouts (the settlements Alternative Payments sends to the partner) with optional filters by status, customer, invoice and a date range.

Webhooks

Tool	What it does
`altpay_create_webhook_subscription` Pro · Write	Subscribe an HTTPS endpoint to one webhook topic.
`altpay_delete_webhook_subscription` Pro · Destructive	Delete a webhook subscription.
`altpay_list_webhook_events` Free · Read-only	List the webhook events Alternative Payments generated for the partner, with delivery status pending, sent or failed, optionally by topic, status and a date range.
`altpay_list_webhook_subscriptions` Free · Read-only	List the partner's webhook subscriptions (topic, endpoint URL, active flag and the last 4 digits of the secret), optionally by topic or active state.
`altpay_retry_failed_webhooks` Pro · Write	Retry ALL failed webhook events for the partner.

Account

Tool	What it does
`altpay_get_partner_theme` Free · Read-only	The partner's branding as customers see it: partner_name and the theme color and logo_url.

Hosted checkout

Tool	What it does
`altpay_checkout_address_autocomplete` Free · Read-only	Address suggestions for the checkout address form, from Google Places, on the payer's side of the API.
`altpay_checkout_calculate_card_fees` Free · Read-only	Calculate the fee split for charging an amount on a saved card, from the checkout lane.
`altpay_checkout_create_bank_account` Pro · Destructive	Save a bank account (ACH) for the checkout customer, as the payer's own checkout would.
`altpay_checkout_create_card` Pro · Destructive	Save a card for the checkout customer from an Evervault card token.
`altpay_checkout_create_payment` Pro · Destructive	Pay the checkout's invoice from a saved payment method, as the payer's checkout would.
`altpay_checkout_get_address_details` Free · Read-only	The full address for a place_id picked in the checkout address form, from Google Places.
`altpay_checkout_get_card_form_credentials` Free · Read-only	The Evervault app_id and team_id the card form needs inside checkout (public identifiers, not secrets).
`altpay_checkout_get_invoice` Free · Read-only	The invoice as the payer's checkout sees it: id, number, status, due date, currency, total (face value) and sub_total (the outstanding balance).
`altpay_checkout_get_invoice_pdf_link` Free · Read-only	The PDF download link for the checkout's invoice.
`altpay_checkout_get_pass_through_fees` Free · Read-only	The card fees that pass through to the checkout customer for the given card networks.
`altpay_checkout_get_theme` Free · Read-only	The partner's theme as the payer's checkout is styled: partner_name, color and logo_url.
`altpay_checkout_list_payment_methods` Free · Read-only	The payment methods saved for the checkout customer: cards (brand, last4, expiry) and bank accounts, with the default flagged.
`altpay_checkout_register_card_cvv` Pro · Write	Register an encrypted CVV token for one saved card, scoped to the checkout's invoice.
`altpay_create_checkout_token` Pro · Write	Mint a one-hour checkout token for one customer and invoice: a bearer that lets the payer pay THAT invoice and add a payment method.

Financial Analytics

Tool	What it does
`altpay_anomaly_and_duplicate_detection` Pro · Read-only	Catches double billing and double charging early: duplicate invoices, duplicate payments, duplicate refunds and unusually large invoices or payments.
`altpay_ar_aging_report` Pro · Read-only	Receivables aging: the open balance by days past due, per customer, with the balance-weighted average lateness.
`altpay_autopay_adoption_report` Pro · Read-only	Whether Autopay pays off: customers with and without a saved default payment method compared on paid share, overdue balance and payment mix.
`altpay_cash_application_gaps` Pro · Read-only	Finds money that went missing between invoice and bank, in four checks.
`altpay_cash_cycle_timeline` Pro · Read-only	Where cash waits, separating customer delay from settlement delay.
`altpay_cash_flow_forecast` Pro · Read-only	Cash-in forecast week by week for up to 26 weeks: expected customer collections with a low and high bound, and expected bank deposits.
`altpay_chargeback_and_refund_analysis` Pro · Read-only	Chargeback and refund ratios against a threshold, to protect the merchant account.
`altpay_collections_priority_list` Pro · Read-only	Whom to chase today and how: overdue invoices ranked by balance, lateness and payment risk, each with a suggested action.
`altpay_customer_account_statement` Pro · Read-only	One customer's statement: chronological ledger lines, running balance, closing balance and aging, to answer what a customer owes and why.
`altpay_customer_financial_360` Pro · Read-only	The account-review pack for one customer, for QBRs and renewals.
`altpay_customer_payment_behavior_scores` Pro · Read-only	A 0 to 100 payment-behavior score and A to F grade for each customer, to decide terms, prepayment or Autopay.
`altpay_dso_analysis` Pro · Read-only	Days sales outstanding: how many days of invoicing are sitting unpaid, with best-possible DSO and average days delinquent.
`altpay_dunning_effectiveness` Pro · Read-only	Whether payment reminders work.
`altpay_expiring_payment_methods` Pro · Read-only	Saved cards that have expired or will within a window, with each customer's open receivables and recent billing attached.
`altpay_failed_payment_analysis` Pro · Read-only	Where payments fail and what it costs: failure rates overall, by method and by customer, how much was recovered, and the revenue still at risk.
`altpay_fee_pass_through_analysis` Pro · Read-only	Who pays the processing fees, and what passing card fees to customers would save.
`altpay_late_fee_and_interest_report` Pro · Read-only	Late-fee and interest income, by month and customer, and who keeps paying late.
`altpay_line_item_revenue_mix` Pro · Read-only	Which services earn the money, from invoice line items, with a trend between the first and second half of the window.
`altpay_monthly_close_pack` Pro · Read-only	The month-end numbers in one call: invoiced, collected (gross and net), refunds, chargebacks, fees by type, deposits, money in transit at month end and receivables.
`altpay_payment_method_mix_and_fee_cost` Pro · Read-only	What each way of getting paid costs, with a card-to-ACH what-if.
`altpay_payout_forecast` Pro · Read-only	When cash lands in the bank, day by day for up to 60 days, for treasury timing.
`altpay_payout_reconciliation` Pro · Read-only	Checks that each bank payout equals the transactions behind it, for month-end bank reconciliation.
`altpay_period_over_period_trends` Pro · Read-only	The business-review series by month, quarter or week, with change on the previous period and on the same period a year earlier.
`altpay_recurring_revenue_estimate` Pro · Read-only	Estimated MRR, ARR, month-by-month movements and net and gross revenue retention, inferred from invoices because the API has no subscription object.
`altpay_revenue_at_risk` Pro · Read-only	Churn and loss signals per customer, with the monthly revenue those customers represent.
`altpay_revenue_concentration` Pro · Read-only	How much of the business rides on a few customers.
`altpay_webhook_delivery_health` Pro · Read-only	Whether the webhook feed to your PSA or accounting system is being delivered, with failed and pending events by topic.

Was this helpful?

Still need help? Ask the team