When a payment fails, Odus normalizes the processor-specific error into a standardized error code. Regardless of whether the payment was routed through Stripe, Adyen, PayPal, or any other gateway, the error response uses the same set of codes. This lets you build a single error-handling path in your integration instead of mapping each processor's errors individually.
Quick answers to the most common questions merchants ask about Odus.
Most Odus API endpoints that return lists of resources (e.g. GET /payments) support pagination, filtering, and sorting to help you retrieve data efficiently. This page describes the available options and how to use them.
Complete reference for the OdusCheckout class, its methods, and TypeScript types.
Complete API reference for the OdusElements class, BaseElement class, and all TypeScript types.