'%20filter='url(%23b)'%20transform='translate(0%20-286)'/%3e%3cpath%20d='M1636.5%20147c-123.436%200-223.5%20102.975-223.5%20230s100.064%20230%20223.5%20230S1860%20504.025%201860%20377c-.143-126.964-100.124-229.853-223.5-230Zm107.16%20308.341c-1.892%202.323-4.973%203.231-7.78%202.295l-98.896-32.908-98.896%2032.908c-2.807.933-5.884.022-7.774-2.3-1.89-2.32-2.212-5.587-.815-8.25l101.128-192.49c1.376-2.238%203.776-3.596%206.357-3.596%202.58%200%204.981%201.358%206.357%203.596l101.128%20192.49c1.401%202.663%201.08%205.932-.81%208.255Z'%20fill='url(%23c)'%20filter='url(%23d)'%20transform='translate(0%20-286)'/%3e%3c/g%3e%3c/svg%3e)
Billing and invoices
Commercial controls in Loopback sit at organization scope: payment methods, invoices, and cost summaries. Exact payment processor (the codebase integrates Stripe for webhooks and payment method flows) and accounting exports (for example SevDesk references appear in invoice routes) depend on operator configuration.
Payment methods
APIs list, add, and manage payment instruments for an organization. Operations are RBAC-gated at organization scope. Primary method selection drives automatic charges where billing automation is enabled.
Invoices
v2 organization invoice endpoints return structured invoice rows and may expose PDF passthrough responses for download. Listing is typically audit-logged. Treat invoices as the legal mirror of usage; cost summaries are operational rollups.
Cost summaries
Cost summary routes aggregate spend and allocation hints for dashboards. Numbers are only as accurate as the billing integration and metering hooks your operator enabled.
Billing agreements (system)
System routes manage billing agreements - commercial pricing overrides, credits, and negotiated rates tied to catalog items (for example compute profiles). Customers usually see effects as price display changes, not direct editing of agreements.