Skip to main content

9 docs tagged with "Reference"

View all tags

Customer value report

The Customer value report shows what your customers are worth over time. Each customer is counted once, placed by their first charge, and everything they pay afterwards counts with that first charge as upsells and rebills. Choose it in the Report menu of Explore.

Error Codes

When a payment fails, ODUS reports the reason as a standardized error code. Where the failure came from a payment processor, the processor-specific error is normalized into that same set — so regardless of whether the payment was routed through Stripe, Adyen, PayPal, or any other gateway, the error response uses the same codes. This lets you build a single error-handling path in your integration instead of mapping each processor's errors individually.

Error Responses

Every request the ODUS API rejects answers with the same JSON body, whatever went wrong:

Pagination, filtering, sorting

Core API v2 paginates by cursor only. page and pageSize are not part of the v2 contract, and v2 also changes filtering semantics and the set of list endpoints.

Payments report

The Payments report counts your payments and what became of them — approved, declined, incomplete or abandoned — with the revenue, refunds and chargebacks behind them. Choose it in the Report menu of Explore.

Projected billing report

The Projected billing report shows the subscription charges coming up. Each active subscription counts once, by its next scheduled charge: a rebill, which is its next renewal, or a recycle, which is the next retry of a renewal that failed. Choose it in the Report menu of Explore.

SDK Reference

Complete reference for the OdusCheckout class, its methods, and TypeScript types.

SDK Reference

Complete API reference for the OdusElements class, BaseElement class, and all TypeScript types.