Docs
[PYMNT]

Invoices

Invoices in PYMNT are a core financial object used to request and track payments between a merchant and their customers.

They represent a structured record of a transaction, including what was purchased, the amount due, and the payment status.

What is an invoice?

An invoice is a payment request created by a merchant.

It contains:

  • A list of items or services
  • The total amount due
  • Payment terms and currency
  • A unique reference identifier
  • The current payment status

Invoices are used for both manual billing and automated payment flows within PLTFRMS.

Invoice lifecycle

An invoice typically moves through several states:

  • Draft — invoice is being created or edited
  • Issued — invoice is sent to the customer
  • Pending payment — waiting for payment to be completed
  • Paid — payment has been successfully received
  • Overdue — payment was not completed in time
  • Cancelled — invoice is no longer valid

Each state is tracked in real time within the PYMNT system.

Creation and management

Invoices can be created through:

  • The PYMNT API
  • Hosted checkout flows
  • Internal merchant systems
  • Automated workflows and integrations

Once created, invoices can be managed, updated (if still in draft), and monitored through the platform.

Payment handling

When an invoice is paid, PYMNT:

  • Processes the payment via the PSP infrastructure
  • Links the transaction to the correct merchant and administration
  • Updates the invoice status automatically
  • Triggers related events for downstream systems

This ensures consistent and traceable payment handling across the platform.

Integration with administrations

Every invoice is linked to an administration, ensuring proper financial structuring.

This allows merchants to:

  • Separate invoices by business unit or entity
  • Maintain clear accounting boundaries
  • Generate structured financial reports

Hosted invoice experiences

Invoices can also be presented through hosted interfaces provided by PLTFRMS.

This allows customers to:

  • View invoice details
  • Pay securely via supported payment methods
  • Receive real-time payment confirmation

No custom implementation is required to accept payments.

Use cases

Invoices are commonly used for:

  • Service billing
  • Subscription and recurring payments
  • One-time purchases
  • Business-to-business transactions
  • Internal cost allocation

Why invoices matter

Invoices are the foundation of financial activity in PYMNT.

They ensure:

  • Clear and traceable payment requests
  • Reliable integration with merchants and administrations
  • Automated and secure payment processing
  • Consistent financial reporting across PLTFRMS