Omisev1.0.1

A SaaS team needs to bill subscribers monthly without storing card data on their own servers. They use create_customer to associate each subscriber with a reusable Omise customer profile, then charge against that customer on each renewal cycle. list_charges and get_charge support reconciliation and failed-payment follow-up.

An online retailer in Thailand needs to match Omise transactions against daily order reports. The skill's list_charges action pulls charges for a date range, while get_charge retrieves full detail for disputed or missing transactions. get_balance gives the merchant a real-time view of funds available for payout.

A two-sided marketplace creates and maintains Omise customer records for buyers and sellers so payment methods can be reused across orders. update_customer keeps email, description, and metadata in sync with the internal user profile, and delete_customer enforces account closures and data-retention policies.

A support team investigates customer complaints about missing or duplicate charges by pulling charges and customer histories through get_charge, list_charges, and get_customer. Agents can quickly confirm charge status, currency, and metadata without leaving the support workflow. Findings are relayed to finance for adjustments or refunds handled outside this skill.

An agency that collects client payments through Omise monitors incoming balances to time its own vendor payouts. get_balance shows transferable and on-hold amounts, while get_account confirms the connected merchant identity. The agency uses this to forecast cash flow and flag any settlement delays.

A platform built on Omise that offers card acceptance, customer vaulting, and recurring billing to merchants as a managed service. It abstracts Omise's API behind its own product experience and charges merchants per transaction or monthly.

A managed billing service where the provider uses Omise customers to store payment references and orchestrates recurring charges on behalf of subscription businesses. The service handles retries, dunning, and reconciliation reporting.

A marketplace operator uses Omise to manage buyer and seller payment profiles, consolidate charge history, and monitor settlement balances. The orchestration layer sits on top of Omise and coordinates payouts and account lifecycle within the platform.