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.
Every request the ODUS API rejects answers with the same JSON body, whatever went wrong:
Quick answers to the most common questions merchants ask about ODUS.
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.
Complete reference for the OdusCheckout class, its methods, and TypeScript types.
Complete API reference for the OdusElements class, BaseElement class, and all TypeScript types.