Developer portal
Apps, API keys, webhooks, request logs, your merchants and these docs in one place at developers.inkress.com.
Changes to the API, webhooks, apps and payments that matter when you build on Inkress.
Apps, API keys, webhooks, request logs, your merchants and these docs in one place at developers.inkress.com.
POST /billing_subscriptions/:uid/charge bills a subscriber straight away without moving their next billing date, and billing history shows only the subscription it belongs to.
Orders, checkout sessions and subscription renewals only show paid once the payment has fully completed, and delayed confirmations catch up on their own. orders.paid follows the same rule.
POST /billing_subscriptions/:uid/card-update-link gives subscribers a secure page to replace their card. A small temporary hold checks the new card first.
The first payment on a subscription sets up an authenticated agreement with the card networks, and every renewal refers to it. Better approval rates, no prompts on renewal.
A business must finish identity verification before it can take any payment, payment links included.
Authentication results are confirmed between Inkress and the card networks instead of relying on the customer's browser, so fewer payments are lost after a successful check.
A two-column app submission form. Listing changes are reviewed without blocking your work.
Strong customer authentication is required on every card transaction, and only a fully verified result can complete a payment. Checkout handles it; no code changes.
The payment-link checkout is a two-pane page with one status page from payment to receipt, and an order-tracking timeline.
Nothing in the browser can approve a payment. Each checkout is confirmed by Inkress against the exact merchant, amount and currency before money moves.
See your published apps' logos, banners and directory listing together.
Installs, subscribers and revenue per app, webhook secret rotation, and handle-based listing URLs.
Merchants browse third-party Inkress apps by search and category, with a page per app.
Webhooks for orders an app created are signed with that app's own secret and delivered to every endpoint the app registered.
Register apps with logos, verify contact details, enrol an authenticator, and follow a step-by-step integration guide.
Apps connect to merchant accounts through a consent screen with scoped permissions. Merchants review and revoke access from Connected apps.
Balances are held per currency, each with its own ledger.
Start a checkout, pay and follow the result on one hosted page, with strong authentication built in. POST /checkout/sessions.
Bill subscriptions by usage and offer trial periods, with subscriptions.trial_ending before a trial ends.
Your systems get told about orders and account events as they happen.
Transaction limits scale with the business's verification level.
Plans, subscribers and automatic card charges each cycle, in JMD or USD.
Billing plans for merchants.