# Integration Testing and Go-live Preparation

Use this guide after writing integration code, before discussing launch readiness, or when the user asks how to configure credentials or test the integration.

Read [Integration Checklist](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/checklist.md) before finalizing code or launch-readiness guidance.

## Credentials and configuration

When guiding credentials and config, include credential locations:

- API domain, Client ID, and Antom public key can be found in [Quick Start](https://dashboard.antom.com/global-payments/developers/quickStart).
- The merchant private key can be generated or managed in [iKeys](https://dashboard.antom.com/global-payments/developers/iKeys); keep it server-side and never log, expose, or commit it.

## Help the merchant run and check the integration

After code is written, do not stop at "code is done". Guide the user through the applicable steps below. Reuse the product, language, and configuration already established in the conversation.

| What the merchant needs | What to do | Read |
| --- | --- | --- |
| Register or configure credentials | Based on the merchant's account and credential readiness, guide registration, retrieval of the credentials needed for integration, or completion of the application's configuration. | [Onboarding Guide](https://cdn.marmot-cloud.com/page/antom-integration-doc/integration-guides/onboarding.md) |
| Test a local notification endpoint | Based on the test objective, guide the merchant to simulate a notification or forward sandbox notifications to the local endpoint, then verify signature checking, acknowledgment, and the corresponding business processing against the selected notification's requirements. | [Antom CLI Webhook Guide](https://cdn.marmot-cloud.com/page/antom-integration-doc/integration-guides/cli-notification.md) |
| Run a sandbox payment | Provide the applicable test data and instructions for the selected product, integration mode, and payment method to help the merchant run the sandbox payment flow. | [Sandbox Guide](https://cdn.marmot-cloud.com/page/antom-integration-doc/integration-guides/sandbox-guide.md) |
| Prepare for launch | Remind the merchant to check items that sandbox testing cannot cover or does not automatically assess, including production configuration, notification reliability, and business logic. Identify what remains unverified. | [Self-Check List](https://cdn.marmot-cloud.com/page/antom-integration-doc/integration-guides/self-check.md) |
| Finish a Billing integration | For the operations used by the current Billing scenario, check resource relationships, API and SDK usage, state handling, and failure recovery against the documentation. | [Billing Self-check](https://cdn.marmot-cloud.com/page/antom-integration-doc/integration-guides/billing-self-check.md) |
| Investigate a failed API call or notification test | Follow the troubleshooting guide to collect evidence, check API documentation, and perform applicable local checks. Verify any repair and escalate diagnosis when the guide's conditions are met. | [Troubleshooting Guide](https://cdn.marmot-cloud.com/page/antom-integration-doc/troubleshoot/troubleshooting-guide.md) |

If the user asks about credentials, registration, local notification debugging, sandbox testing, checklist, self-check, or go-live readiness at any point, read the matching document and answer the question then. For a checklist question, use Integration Checklist above.

Use the Antom CLI Webhook Guide when the user needs to verify or debug notification handling in the local application. A question about a notification field or a synchronous operation does not require installing or running the CLI.