# Antom Account & Credentials Onboarding

> Used by Agent to confirm the user's account state ONCE per session, triggered when the user first asks to "write code / build demo / test in sandbox / go live", OR when Agent detects that the code under discussion needs Antom credentials (gateway URL / ClientId / private key / Antom public key) but they are missing or still placeholder. Then route to the matching branch. Do NOT re-ask in the same session.

## Trigger rule

Ask the user which state they are in (A / B / C). Do NOT re-ask in the same session.

- **State A** — Not registered with Antom yet
- **State B** — Registered, but has not retrieved sandbox gateway URL / ClientId / keys
- **State C** — Already has sandbox gateway URL, ClientId, and key pair

---

## State A: Not registered

1. **Register entry**: https://www.antom.com/contact-us/
   - Submit the contact form. Antom will notify you within **1 business day** with an invitation email; click **Register now** in that email to start.
   - (Alternative entry with skill tracking) https://www.antom.com/start-now?portal_channel=Antom_Website_Developer_Community&utm_source=developer_community&utm_medium=referral&utm_campaign=dev_register&utm_content=skill
2. **Full registration walkthrough**: https://docs.antom.com/ac/merchant_service/merchant_onboard.md
   - Four steps: apply for Dashboard account → create Dashboard account → register merchant account → activate merchant account.
   - Merchant account review takes up to **1 business day**.
3. **What the user can do in parallel while waiting for review**
   - Read product / SDK docs (see SKILL.md `Get Integration Documentation`).
   - Build code skeleton with placeholder gateway URL, ClientId, and keys. Fill in real values once issued.
   - Choose target payment methods and integration mode in advance.

> Agent MUST explicitly warn the user about the review wait time, and offer the parallel actions above so the user is not blocked.

---

## State B: Registered, no keys yet

1. **Dashboard login**: https://dashboard.antom.com (switch to **Sandbox** mode)

2. **Retrieve all four values from the same Dashboard location**:
   **Developer** > **Quick Start** > **Integration resources and tools** > **Integration resources** (https://dashboard.antom.com/global-payments/developers/quickStart)

   | # | Field | How to get |
   |---|---|---|
   | 1 | **Gateway URL** | Copy from the page above (Dashboard displays the URL matching the merchant's registered region). Verify against the region→gateway table in `faq-coding.md` item 1 if unsure. |
   | 2 | **ClientId** | Copy from the page above. |
   | 3 | **Merchant private key** | On the Dashboard, click **Generate key** — Antom generates and displays the private key once (copy immediately; Antom does not store it). Or use **Replace keys → Use your own** with the Antom-provided offline tool if you want to generate the key pair locally. |
   | 4 | **Antom public key** | Download from this page; used to verify Antom responses & notifications. |

3. **Agent behavior when generating code**
   - Leave all four fields as empty placeholders — never pre-fill on behalf of the user.
   - Add an inline comment **in the user's working language** above each placeholder, stating the purpose and retrieval path.
   - Do NOT proceed to run/test the code until the user confirms each value is filled.

4. **Check settlement currencies**
   - While in **Sandbox** mode, go to **Finance** → **Overview**: https://dashboard.antom.com/global-payments/finance/overview
   - Confirm how many currencies are contracted; if multiple, `settlementCurrency` is required in code (see `faq-coding.md` item 3 for details).

5. **Key handling**
   - All key storage and usage rules MUST follow SKILL.md `Security Red Lines`.

---

## State C: Has sandbox gateway URL, ClientId, and keys

- If any of the four values (gateway URL / ClientId / private key / Antom public key) is missing, retrieve it via State B step 2 first.
- Otherwise proceed directly to sandbox end-to-end experience: see [Sandbox Experience Guide](https://cdn.marmot-cloud.com/page/antom-integration-doc/integration-guides/sandbox-guide.md).

---

## Going live (required before production)

Sandbox does NOT require payment-method activation, but production DOES.

1. Log in to https://dashboard.antom.com and switch to **Live mode**.
2. Apply for each payment method individually or in batch: https://docs.antom.com/ac/merchant_service/enable_payment.md
   - Activation requires additional information (company representative, company info, card payment questionnaire, etc.) and is subject to review.
3. Production gateway URL, production ClientId, production keys — all differ from sandbox. Pre-launch switching checks are covered by the Pre-launch Verification section of the online [Integration Checklist](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/checklist.md) (referenced from SKILL.md `Integration Validation`).

> Production payment-method activation review time is independent of merchant account onboarding. Plan ahead.