# Use now, pay by invoice later. Postpaid.

Energy, bandwidth, address activation, AML checks and other services without a prepaid deposit. One agreement, shared spending controls and settlement in the currency agreed for your business.

For approved business accounts after KYB and contract agreement. Available currencies, payment methods and credit limits are confirmed before activation.

## Built for operations and finance

### Shared credit

One account-level limit across supported services.

### Your controls

Set lower overall and product spending limits through the API.

### Contract currency

Agree fiat or supported digital-asset settlement before activation.

### Clear records

Invoices and itemised usage records for reconciliation.

## Keep delivery moving. Keep spending visible.

### Spend within an approved limit

Netts sets the account credit limit. Your team can set additional overall or product limits inside it. Product limits do not create extra credit.

### Choose terms that fit your business

The agreement defines the contract currency, supported payment method, billing period and payment terms. Network details are specified for crypto payments; fiat uses agreed payment instructions.

### Give finance a clear audit trail

Match order IDs and supplied services with recorded charges, payments and adjustments. Receive invoices and usage records for your accounting workflow.

### Start with verified business onboarding

Complete KYB, confirm the contracting entity and billing details, and agree credit and service coverage. Activation follows approval; it is not an automatic credit offer.

## From agreement to production

### Tell us how you operate

Share your services, expected volumes and preferred currency.

### Complete KYB and agree the contract

Confirm business details, service coverage, credit limits and settlement terms.

### Connect and reconcile

Use the supported order APIs, manage your own spending limits and reconcile recorded usage with invoices.

## Before you connect

### Do we need a separate API for Postpaid?

No. Postpaid is a Netts product for approved business accounts: you order through the same Netts APIs, and services are billed by invoice instead of being paid from a deposit.

### Can we pay in fiat or cryptocurrency?

Yes, on agreed terms. The contract specifies the currency and supported payment method. A currency or network must be confirmed as supported before the account is activated for it.

### Can our team increase the credit limit?

Only Netts can change the administrative credit limit. Your team can create, change or disable its own additional limits inside that ceiling.

### Are product limits separate balances?

No. They share the same account credit. Setting a maximum for each service does not multiply the total credit available.

### What does accounting receive?

Invoices and itemised service records for the agreed billing period, with order references, charges, payments and applicable adjustments. The agreement defines delivery and settlement terms.

## Plan your postpaid integration

Tell us your volumes, services and preferred contract currency. We will confirm the available setup and onboarding requirements.

[Discuss postpaid terms](https://t.me/netts_io) · energy@netts.io

## Documentation and AI access

The Markdown version contains the same product information. The documentation MCP is read-only: it does not access an account or place orders.

[Read the API documentation](https://doc.netts.io/api/v2/postpaid.html) · [OpenAPI](https://doc.netts.io/openapi.yaml)

[Documentation MCP](https://doc.netts.io/api/mcp) · MCP: https://doc.netts.io/mcp