Go live with ICEPAY
Complete your testing, prepare your production integration, and process your first live payment with ICEPAY.
You are ready to go live when your merchant is configured, your integration has been tested successfully, and you are ready to process real customer payments.
Live mode processes real payments. Complete the checks on this page before switching your merchant or integration to production.
Before you go live
Section titled “Before you go live”Confirm that:
- You have completed a successful end-to-end payment in Test mode.
- Your integration uses the correct Merchant ID.
- Your production credentials are available and stored securely.
- Your Redirect URL is configured and reachable, if your integration uses redirects.
- Your Webhook or postback URL is configured, publicly reachable, and able to process payment status updates.
- The payment methods you want to offer have been confirmed for your merchant.
- Your checkout branding and merchant information are correct.
- Your system handles successful, pending, failed, cancelled, and expired payments.
- Your system handles webhook or postback retries safely.
- Your refund process has been tested or documented.
- Your pricing, fees, payouts, and settlement expectations have been reviewed with ICEPAY.
- Your merchant secret and other credentials are handled only on your server.
Prepare your production integration
Section titled “Prepare your production integration”Before changing the merchant to Live mode, review your application configuration.
Your production integration should:
- Use the production Merchant ID.
- Use production credentials rather than test credentials.
- Keep the merchant secret on your server.
- Never expose credentials in browser JavaScript, mobile applications, client-side code, or public repositories.
- Send the correct currency, amount, reference, and customer information.
- Store the ICEPAY payment reference returned when a payment is created.
- Verify payment status using the server-side response or webhook/postback.
- Treat the webhook or postback as the source for updating the order status.
- Avoid marking an order as paid only because the customer returned to your success page.
If your application uses environment variables, update the production environment without committing secrets to source control.
Switch your merchant to Live mode
Section titled “Switch your merchant to Live mode”-
Confirm that the correct merchant is selected
Sign in to the ICEPAY Portal and select the ICEPAY Account and merchant that you want to use for live payments.
If you have more than one merchant, verify the Merchant ID and business details carefully before continuing.
-
Review the merchant configuration
Confirm that the merchant details, website URL, payment methods, checkout branding, Redirect URL, and Webhook or postback URL are correct.
Some settings may require configuration or approval by ICEPAY. If an expected setting or payment method is unavailable, contact ICEPAY before continuing.
-
Confirm your integration is ready
Verify that your production application is deployed or ready to deploy with the correct production credentials and configuration.
Test the full order flow, including payment creation, checkout, redirects, webhook or postback handling, order updates, and error handling.
-
Switch to Live mode when available
In the Portal, use the merchant’s processing-mode setting to switch from Test to Live or production mode, if this option is available for your configuration.
-
Update your production application
Deploy the production configuration using the Live Merchant ID, production credentials, and the production settings confirmed with ICEPAY.
-
Make a controlled live payment
Create one small live payment using a controlled order or internal test purchase.
Use a recognizable payment reference so that you can identify the transaction in both your system and the ICEPAY Portal.
-
Verify the result
Confirm that:
- ICEPAY shows the expected payment status.
- Your webhook or postback endpoint received the payment update.
- Your merchant system updated the order correctly.
- The shopper was redirected to the expected success or failure page.
- The payment reference is stored with the order.
- The amount and currency are correct.
Verify your first live payment
Section titled “Verify your first live payment”After the payment is completed, verify the transaction in both systems.
In the ICEPAY Portal
Section titled “In the ICEPAY Portal”Check the payment using its reference. Confirm the:
- Amount and currency.
- Merchant.
- Payment method.
- Payment status.
- Creation and update time.
- Test or Live environment.
In your merchant system
Section titled “In your merchant system”Confirm that your system:
- Received the webhook or postback.
- Validated the received payment information.
- Updated the order only after receiving a valid successful status.
- Stored the ICEPAY payment reference.
- Displayed the correct order status to the customer.
- Handled the redirect independently from the server-side payment notification.
After launch
Section titled “After launch”Once live payments are working:
- Monitor payments and failed transactions regularly.
- Monitor webhook or postback failures and retry processing where necessary.
- Reconcile payments with your orders.
- Review payouts and settlement reports.
- Use the documented refund process when a customer must be refunded.
- Keep production credentials and recovery information secure.
- Restrict access to the ICEPAY Portal and production systems.
- Keep your integration and error logs available for troubleshooting.
- Contact ICEPAY before changing important merchant or payment-method settings.
Troubleshooting
Section titled “Troubleshooting”I cannot switch my merchant to Live mode
Confirm that you selected the correct merchant and that onboarding, compliance, and required merchant configuration are complete.
Some merchants require additional configuration or approval before Live mode becomes available. Contact ICEPAY Support or your account administrator with your Merchant ID and the message shown in the Portal.
Never send your merchant secret in a support request.
A production payment method is unavailable
Payment-method availability can depend on your merchant configuration and the agreement with ICEPAY.
Confirm that the payment method is enabled for the correct merchant and contact ICEPAY with your Merchant ID and the payment method you want to use.
Do not rely on a payment method in production until ICEPAY confirms that it is available.
The webhook or postback was not received
Confirm that the endpoint:
- Is publicly reachable from the internet.
- Uses the correct production URL.
- Accepts the HTTP method and content type sent by ICEPAY.
- Returns a successful response after processing the notification.
- Does not block ICEPAY requests with authentication, firewall, or IP restrictions.
- Logs failed requests safely without recording secrets.
Check your server and application logs. If you contact ICEPAY Support, include the payment reference, Merchant ID, approximate time, HTTP response details, and relevant error messages. Do not include credentials or merchant secrets.
The payment status has not been updated
Refresh the payment in the Portal and confirm that you are viewing the correct merchant and account.
Check whether your webhook or postback endpoint received the notification and whether your application returned an error. Confirm that your application supports the payment statuses used by your integration.
Contact ICEPAY Support with the payment reference, Merchant ID, timestamp, and error details if the status remains incorrect.
The live payment result was unexpected
Do not fulfil or refund the order until the payment status is confirmed.
Compare the payment reference, amount, currency, merchant, and status in the Portal with the values stored by your system. Check your webhook or postback logs and application logs for processing errors.
If you need help, provide ICEPAY Support with the payment reference, Merchant ID, approximate time, and a description of the expected and actual result. Never provide payment credentials or your merchant secret.

