iSolutions

iSolutions is a payment processor that handles credit card and alternative payment transactions at checkout and on invoice payments. Stores use this integration to securely process customer payments through iSolutions' payment gateway.

How to set it up

Where to find it: Admin → Payments → iSolutions

When you'd use this: When you want to process credit card payments through the iSolutions payment gateway for checkout transactions and invoice payments.

What you need first:

• An active iSolutions merchant account
• Your iSolutions API key (for authentication)
• Your iSolutions subdomain (the unique identifier for your iSolutions account URL)
• Your webhook token (for securing payment confirmation callbacks from iSolutions)

Set it up:

1. Navigate to Admin → Payments → iSolutions
2. Enter your subdomain (this is the unique identifier in your iSolutions URL, e.g., if your URL is yourstore.ipaymentsecure.com, enter yourstore)
3. Enter your apiKey (provided by iSolutions for API authentication)
4. Enter your webhookToken (a secret token that iSolutions will send with payment confirmation webhooks to verify they're authentic)
5. Save the configuration
6. Contact iSolutions support to configure the webhook endpoint URL in your iSolutions merchant portal
7. Test the integration by processing a small test transaction to verify connectivity

Configuration options

Field	What it does	Default	Required
subdomain	The unique subdomain for your iSolutions account that forms part of the payment gateway URL (e.g., yourstore in yourstore.ipaymentsecure.com)	None	Yes
apiKey	The API authentication key provided by iSolutions, used for Basic authentication in the Authorization header	None	Yes
webhookToken	A secret token that iSolutions sends with webhook requests to confirm the webhook is authentic and not forged	None	Yes

Using it day-to-day

For customers at checkout:

1. Customer proceeds to checkout and enters their payment information in the embedded iSolutions payment form
2. Customer submits the payment
3. If the payment is declined (e.g., CVV mismatch, insufficient funds), the customer can correct their card details or enter a different card without starting over
4. Customer resubmits the corrected payment information
5. Once iSolutions approves the payment, the system verifies the transaction using the verifyTransaction operation and completes the order

For invoice payments:

1. Customer views their open invoices
2. Customer selects invoices to pay and proceeds to payment
3. Payment is processed through the iSolutions gateway using the same flow as checkout
4. Once approved, the invoice is marked as paid in the system

Behind the scenes:

• The system automatically waits for the embedded payment form to fully load and initialize before allowing payment submission
• When iSolutions reports a declined payment, the system leaves the payment session active to allow retry attempts
• After successful payment, the system calls the verifyTransaction endpoint to confirm the transaction with iSolutions before completing the order
• The last four digits of the credit card number are written to the order's work description for reference
• iSolutions sends a payment confirmation webhook to the system as a backup when the customer's payment succeeds, ensuring orders are marked as paid even if the payment response from the checkout page doesn't reach the system
• The webhook uses the unique order reference to prevent duplicate charges if both the checkout response and the webhook arrive
• If the webhook arrives while the checkout page is still processing the same payment, the system reconciles both signals to complete the order exactly once

Troubleshooting

Customer sees "An unexpected error occurred" but the order wasn't created This indicates a communication issue with the payment gateway, not a declined payment. The customer should refresh the checkout page and try again. If the problem persists, verify that the subdomain and apiKey are configured correctly, and check that the iSolutions gateway is accessible at https://[subdomain].ipaymentsecure.com.

Payment form doesn't appear or seems unresponsive The payment form may not have fully initialized. Refresh the checkout page to reload the form. If the problem persists, check browser console errors and verify that the iSolutions iframe can load properly (check for content security policy restrictions or network issues).

Customer retried with a different card but checkout didn't complete Verify that the customer clicked the submit button after entering the new card details. If the payment form doesn't respond, the customer may need to refresh the checkout page and start the payment process again.

Payment was processed but the order wasn't created The system receives payment confirmations from iSolutions through both the checkout page and a backup webhook. If the checkout page lost connection but the webhook was received, the order should still be created. Wait a few moments and refresh the orders list. If the order still doesn't appear after several minutes, contact support immediately with the transaction timestamp and any customer confirmation from iSolutions to investigate the payment-order mismatch.

Payment shows as declined but customer's card was actually charged Verify the transaction status directly in your iSolutions dashboard. Use the referenceNumber to look up the transaction. If the charge was successful in iSolutions but failed in CommerceBuild, the verifyTransaction call may have timed out or returned an unexpected response code. Contact support with the reference number to reconcile the transaction.

Pre-authorized payments aren't capturing correctly for invoice payments Verify that the payment configuration for invoice payments is set to capture rather than pre-authorize. Check the payment settings to ensure invoice payments are configured to complete the transaction rather than only authorizing the charge.

Webhook endpoint configuration The webhook endpoint URL must be configured in your iSolutions merchant portal by iSolutions support. Provide them with the webhook URL and the webhook token you entered in the iSolutions payment configuration. If you change the webhook token in CommerceBuild, you must also update it in the iSolutions merchant portal or payment confirmations will be rejected.