Fintech & Payments

This quick start is for companies whose product is moving money: payment facilitators, embedded-finance platforms, and banking-as-a-service providers who charge a percentage of volume plus a per-transaction fee, discount that rate at higher volumes, and sometimes share it with a partner. In Alguna that is a metered product rated by a percentage pricing model over a billable metric that sums transaction amounts. This page shows the setup end to end. The objects involved are described in How Alguna Works.

Common fintech pricing models

Model	How it works	Alguna price type
Percentage + fixed	2.9% of volume + $0.30 per transaction	Two metered products: `volume_percentage` on transaction amount, `unit` on transaction count — or one `expression` price
Volume tiers	Lower rates at higher monthly volume	`volume_percentage` (whole volume at the tier reached) or `graduated_percentage` (each band at its own rate)
Tiered percentage with caps	Rate steps by volume with a fee cap per tier	`tiered_percentage`
Interchange plus	Interchange + network fee + your markup	`expression` over event properties carrying the interchange amount
Platform fee	Monthly fee + per-transaction	A `fixed` recurring product plus the metered products above

All eleven price types, with the shape of each, are on Pricing models.

Set up

Define the billable metrics

Under Billable Metrics (or POST /metrics), create:

Transaction Volume — sum of the amount property on transaction events.
Transaction Count — count of transaction events.

See Define metrics.

Create the metered products

Under Products (or POST /products), create a metered product per metric with fee_type: "metered" and payment_terms: "arrears" — usage is billed after the period. Set revenue_allocation_method to usage_based so revenue is recognised as volume occurs.

Price them

Attach a volume_percentage or graduated_percentage price to the volume product and a unit price to the count product. For example:

$0 –$ 50,000 per month: 2.9%
$50,000 –$ 250,000: 2.5%
$250,000+: 2.2%

plus $0.30 per transaction.

Bundle into a plan

Put both prices (and a fixed platform fee, if any) into a plan so every merchant is onboarded onto the same offer. See Plans.

Send transactions as events

As transactions settle, post them to POST /events. Ingestion is idempotent on unique_id, so retries are safe.

Sending a transaction

curl -X POST https://api.alguna.io/events \
  -H "Authorization: Bearer $ALGUNA_API_KEY" \
  -H "Alguna-Version: 2026-04-01" \
  -H "Content-Type: application/json" \
  -d '{
    "events": [
      {
        "unique_id": "txn_8f2a91",
        "event_name": "transaction",
        "account": "cust_merchant_42",
        "timestamp": "2026-04-01T10:30:00Z",
        "properties": { "amount": 125.00, "card_brand": "visa", "interchange": 1.87 }
      }
    ]
  }'

import os

import requests

response = requests.post(
    "https://api.alguna.io/events",
    headers={
        "Authorization": f"Bearer {os.environ['ALGUNA_API_KEY']}",
        "Alguna-Version": "2026-04-01",
        "Content-Type": "application/json",
    },
    json={
        "events": [
            {
                "unique_id": "txn_8f2a91",
                "event_name": "transaction",
                "account": "cust_merchant_42",
                "timestamp": "2026-04-01T10:30:00Z",
                "properties": {"amount": 125.00, "card_brand": "visa", "interchange": 1.87},
            }
        ]
    },
    timeout=10,
)
response.raise_for_status()

result = response.json()
if result["failed"]:
    print("rejected:", result["failed"])

See Send usage for batch limits and the response shape.

Billing flow

The invoice lists the rated volume and count as separate lines with the period they cover. Merchants can pay by saved card or bank transfer, and see their statement in the customer portal. See Invoicing Customers.

Fee structures

Percentage + fixed

Component	Amount
Percentage fee	2.9% of transaction volume
Fixed fee	$0.30 per transaction
Example: $100 transaction	$2.90 +$ 0.30 = $3.20

Interchange plus

Interchange varies per transaction, so it has to arrive on the event. Carry it as a property (interchange above), define a metric that sums it, and price your markup as a separate volume_percentage on gross volume. The invoice then shows pass-through interchange and your markup as separate lines. Model the partner as a customer of their own and bill (or credit) them from a separate metered product fed by the same events, or handle the split outside Alguna from the invoice data. Alguna does not split a single invoice between two payees.

Key features

Billable Metrics

Sum, count, and filter transaction events.

Pricing models

Percentage, tiered, and expression prices.

Send usage

Idempotent event ingestion.

Revenue Recognition

Usage-based allocation.

API reference

Ingest events

Send transaction events.

Products

Create metered products.

Invoices

Read monthly statements.

Customers

Onboard merchants.

Hybrid Motion

Self-serve for SMB, sales for enterprise merchants.

Finance & Billing Ops

Collections and revenue recognition.

Developers

API integration for event ingestion.

← Back to Quick Starts

See all quick start guides

Quick Starts

By Industry

By Motion

By Role

Common fintech pricing models

Set up

Sending a transaction

Billing flow

Fee structures

Percentage + fixed

Interchange plus

Key features

Billable Metrics

Pricing models

Send usage

Revenue Recognition

API reference

Ingest events

Products

Invoices

Customers

Hybrid Motion

Finance & Billing Ops

Developers

← Back to Quick Starts

​Common fintech pricing models

​Set up

​Sending a transaction

​Billing flow

​Fee structures

​Percentage + fixed

​Interchange plus

​Partner revenue share

​Key features

Billable Metrics

Pricing models

Send usage

Revenue Recognition

​API reference

Ingest events

Products

Invoices

Customers

​Related quick starts

Hybrid Motion

Finance & Billing Ops

Developers

← Back to Quick Starts

Common fintech pricing models

Set up

Sending a transaction

Billing flow

Fee structures

Percentage + fixed

Interchange plus

Partner revenue share

Key features

API reference

Related quick starts