# Integrated Commerce Omni-Channel Payment API ## Description This is version `2025.09.22` of this API documentation. Last update on Oct 1, 2025. ### Introduction The Integrated Commerce Omni-Channel Payment API is a RESTful API that provides a unified interface for processing payments across multiple channels. This API enables developers to integrate payment processing capabilities into their applications with a single set of endpoints, simplifying implementation and reducing development time. The API supports integration in both the United States and Canada, using USD and CAD currencies. ### Features #### Card Present Transactions The API supports the following Card Present transaction types: - Authorization: Verification with the Issuer if the card is valid for payment. The authorization amount is reserved, but not captured/settled. - Capture: Complete a previously authorized transaction. The cardholder is billed for the transaction, and the transaction is settled to the merchant. - Sale: Combined authorization and capture in a single step. - Refund: Process reversal of a previous sale transaction (automatically performs a void if the transaction is in the current batch, or a refund if already settled) - Void: Cancel a previously completed transaction (sale, authorization or capture) if it is still in the current batch (typically same day) Card Present transactions are processed through Verifone T650c (countertop) and T650p (portable) Android-based payment terminals. #### Card Not Present Transactions For online payments, the API provides Hosted Payment Forms for payment transactions and secure card data collection for tokenization. The API supports the following Card Not Present transaction types: - Authorization: Verification with the Issuer if the card is valid for payment. The authorization amount is reserved, but not captured/settled. - Includes AVS (Address Verification Service) and CVV validation support - Capture: Complete a previously authorized transaction. The cardholder is billed for the transaction, and the transaction is settled to the merchant. - Sale: Combined authorization and capture in a single step. - Includes AVS (Address Verification Service) and CVV validation support - Refund: Process reversal of a previous sale transaction (automatically performs a void if the transaction is in the current batch, or a refund if already settled) - Void: Cancel a previously completed transaction (sale, authorization or capture) if it is still in the current batch (typically same day) - AVS (Address Verification Service) and CVV validation #### Tokenization The API implements a tokenization system that: - Creates payment tokens from both Card Present and Card Not Present transactions - Maintains tokens that work across all channels (in-person and online) - Supports token management operations (create, update, delete) #### Webhooks Real-time notifications via webhooks for: - Transaction events ([sales](#operation-webhooksalecompleted), [authorizations](#operation-webhookauthcompleted), [captures](#operation-webhookcapturecompleted), [refunds](#operation-webhookrefundcompleted), [voids](#operation-webhookvoidcompleted)) - Token operations ([creation](#operation-webhooktokencreated), [updates](#operation-webhooktokenupdated), [deletion](#operation-webhooktokenremoved)) #### Payment Methods The API uses "Payment Methods" as the foundation for processing transactions. Each payment method has a unique paymentMethodId that represents a specific way to accept payments: - **Physical Terminals**: For Card Present, in-person transactions - **Virtual Terminals**: For Card Not Present, online transactions - **Tokenized Cards**: For processing Card On File transactions where customer payment information has been securely stored for recurring or future transactions When you call the [`GET /payment-methods`](#operation-getpaymentmethods) endpoint, the API returns a list of all payment methods available to your account. This includes physical payment terminals for in-store transactions and Hosted Payment Forms that can be embedded in your website, mobile app, or used for email invoices. Each payment method includes details such as its ID, type (physical or virtual), currency, description, and whether it's set as a default. This information helps you determine which payment method to use for different transaction scenarios. #### Account Holder Management The API supports account holder management for organizing and retrieving tokenized payment methods. When processing sale/auth transactions, you can specify an account holder (either by creating a new one or referencing an existing one), and the system will automatically associate tokenized cards with that account holder. This enables you to: - Retrieve all payment methods associated with a specific account holder - Organize customer payment methods by account holder ID (internal or external) - Query an account holder's payment methods with filtering and sorting capabilities When you call the [`GET /payment-methods/account-holder/{accountHolderId}`](#operation-getaccountholderpaymentmethods) endpoint, the API returns a list of all tokenized payment methods associated with a specific account holder. #### Transaction Retrieval The API provides transaction retrieval capabilities that allow you to query and check the status of transactions when processing errors occur. This feature is essential for handling scenarios where API responses are not received due to network timeouts, webhooks fail to deliver, or when a transaction returns an "Interrupted" status indicating unknown final state. When you call the [`GET /transactions`](#operation-gettransactions) (List Transactions) endpoint, the API returns a paginated list of transactions for your account, such as sales, authorizations, token operations, etc. The retrieval endpoint also supports comprehensive filtering and sorting options to help you locate specific transactions or identify processing issues. This ensures you can verify transaction outcomes and prevent duplicate charges when system interruptions occur, maintaining accurate transaction records and customer billing. ### Support For technical assistance, please contact our support team at [support@integratedcommerce.io](mailto:support@integratedcommerce.io). ## Servers - https://api.omni.integratedcommerce.io/v1: https://api.omni.integratedcommerce.io/v1 () ## Authentication ## Topics - [Hosted Payment Form](https://docs.omni.integratedcommerce.io/topic/topic-hosted-payment-form.md) - [Test Cards](https://docs.omni.integratedcommerce.io/topic/topic-test-cards.md) ## Endpoints and operations ### [Transactions](https://docs.omni.integratedcommerce.io/group/endpoint-transactions.md) - [List Transactions](https://docs.omni.integratedcommerce.io/operation/operation-gettransactions.md) - [Sale (Card Present)](https://docs.omni.integratedcommerce.io/operation/operation-salecardpresent.md) - [Sale (Card Not Present)](https://docs.omni.integratedcommerce.io/operation/operation-salecardnotpresent.md) - [Sale (Token)](https://docs.omni.integratedcommerce.io/operation/operation-saletoken.md) - [Auth (Card Present)](https://docs.omni.integratedcommerce.io/operation/operation-authcardpresent.md) - [Auth (Card Not Present)](https://docs.omni.integratedcommerce.io/operation/operation-authcardnotpresent.md) - [Auth (Token)](https://docs.omni.integratedcommerce.io/operation/operation-authtoken.md) - [Capture](https://docs.omni.integratedcommerce.io/operation/operation-capture.md) - [Refund](https://docs.omni.integratedcommerce.io/operation/operation-refund.md) - [Void](https://docs.omni.integratedcommerce.io/operation/operation-void.md) - [Unreferenced Refund (Card Present)](https://docs.omni.integratedcommerce.io/operation/operation-unreferencedrefundcardpresent.md) - [Unreferenced Refund (Card Not Present)](https://docs.omni.integratedcommerce.io/operation/operation-unreferencedrefundcardnotpresent.md) ### [Tokens](https://docs.omni.integratedcommerce.io/group/endpoint-tokens.md) - [Create Token (Card Present)](https://docs.omni.integratedcommerce.io/operation/operation-createcardpresenttoken.md) - [Create Token (Card Not Present)](https://docs.omni.integratedcommerce.io/operation/operation-createcardnotpresenttoken.md) - [Update Token](https://docs.omni.integratedcommerce.io/operation/operation-updatetoken.md) - [Remove Token](https://docs.omni.integratedcommerce.io/operation/operation-removetoken.md) ### [Payment Methods](https://docs.omni.integratedcommerce.io/group/endpoint-payment-methods.md) - [List Payment Methods](https://docs.omni.integratedcommerce.io/operation/operation-getpaymentmethods.md) - [List Account Holder Payment Methods](https://docs.omni.integratedcommerce.io/operation/operation-getaccountholderpaymentmethods.md) ## Webhooks ### [Transaction Notifications](https://docs.omni.integratedcommerce.io/group/webhook-transaction-notifications.md) - [Sale completed](https://docs.omni.integratedcommerce.io/operation/operation-webhooksalecompleted.md) - [Auth completed](https://docs.omni.integratedcommerce.io/operation/operation-webhookauthcompleted.md) - [Capture completed](https://docs.omni.integratedcommerce.io/operation/operation-webhookcapturecompleted.md) - [Refund completed](https://docs.omni.integratedcommerce.io/operation/operation-webhookrefundcompleted.md) - [Void completed](https://docs.omni.integratedcommerce.io/operation/operation-webhookvoidcompleted.md) ### [Token Notifications](https://docs.omni.integratedcommerce.io/group/webhook-token-notifications.md) - [Token created](https://docs.omni.integratedcommerce.io/operation/operation-webhooktokencreated.md) - [Token updated](https://docs.omni.integratedcommerce.io/operation/operation-webhooktokenupdated.md) - [Token removed](https://docs.omni.integratedcommerce.io/operation/operation-webhooktokenremoved.md) [Powered by Bump.sh](https://bump.sh)