Overview

OmniPoint Order Management supports secure payment processing using stored credit cards via CIM (Customer Information Manager), most commonly with Authorize.Net. This article covers how card-on-file payments work, how to troubleshoot issues, and how to manage your payment gateway configuration.

Card on File (CIM) allows merchants to securely store and reuse customer credit card details for future transactions. This reduces the need for customers to re-enter their card information and supports faster order fulfillment, pre-authorizations, and delayed capture.

Payment Options Explained

• Credit Card: A card is entered and charged at time of transaction. No information is stored for later use.
• Account: The transaction is logged as an outstanding balance (e.g. net terms); no immediate payment is captured.
• Card on File (CIM): A previously stored credit card is used for payment without re-entry of card details.

Instructions

Use a Card on File

1. Go to Orders View Orders and select the order you want to charge.
2. Click Apply Payment.
3. Choose Card on File from the list of available payment options.
4. Select one of the stored cards associated with the customer or account.
5. Click Submit to process the payment.

If successful, the payment is recorded against the order. If the order was pre-authorized, you may instead use the Capture and Mark as Shipped option on the pick/pack dashboard.

Manage Authorize.Net Credentials

1. Go to Admin Manage Payment Gateway.
2. Select the gateway (e.g. Authorize.Net).
3. Update your Login ID and Transaction Key with current values.
4. Save changes and reattempt the payment if needed.

It's also important to verify that the Order Guide associated with your transaction is correctly mapped to Authorize.Net under its gateway settings.

Troubleshooting Payment Errors

Common error messages include:

• "Authentication Failed": Indicates expired or invalid API credentials for Authorize.Net.
• "Card Expired": The saved card details are outdated.
• "Transaction Declined": The issuing bank rejected the transaction.

In the event of a failed payment, users can update the stored card, switch to a different method, or contact the customer for a new payment option.

Tips and Best Practices

• Always test your gateway credentials in a sandbox or staging environment before deploying changes.
• Encourage customers to keep their card data updated, especially for recurring orders.
• Use pre-authorization for delayed shipment scenarios, then capture payment only when ready to ship.
• If needed, switch between Account and Card on File for flexibility in B2B sales.