> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amlok.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Account management

> Manage payments and cancellation in the portal, with dedicated account-manager support for enterprise clients.

Use the **client portal** to manage payment methods, automatic top-ups, and account cancellation. Enterprise clients can also work with their dedicated account manager on cancellation, agreements, rates, workload limits, and renewal.

Your account manager provides client portal access information and environment details. Authorized administrators can create workspace-bound API keys in the portal and manage their scopes, expiry, rotation and revocation. The portal also provides registered integration return URLs and webhook destination settings. See [API authentication](https://docs.amlok.io/api-reference/authentication.md) and [integration configuration](https://docs.amlok.io/api-reference/configuration.md).

For assistance, email [support@amlok.tech](mailto:support@amlok.tech?subject=AMLOK%20account%20management) with your company and workspace reference. Do not include full bank or card credentials in email.

## Payments and top-ups

Add or change a **card or bank account** in the portal. Set your automatic top-up trigger at **CAD 200.00 or higher** and the amount at **CAD 500.00 or higher**. CAD 200.00 is an automatic top-up trigger, not a floor. With auto-pay off, processing continues below it while credits cover each operation. Insufficient-credit errors do not debit unprocessed work. Pending payments do not fund new processing; a higher threshold can provide more time for settlement.

Save at least one bank account for refunds, including if you normally fund by card. Your workspace has one credit balance across all products, including promotional top-ups. See [credits and billing](https://docs.amlok.io/pricing/credits-and-billing.md).

## Cancellation and refund

When cancellation is submitted in the portal or set by your account manager, all product processing, usage deductions, and new or scheduled top-ups stop immediately. Pending processing is cancelled without another charge.

1. Export any records you need, confirm the saved refund bank account, and request cancellation in the portal. Enterprise clients may request it through their account manager.
2. You may cancel at any time without notice. AMLOK schedules closure at the end of the request month and reconciles charges already posted and funding already in flight. No processing, usage deductions, or top-ups resume during the closure period.
3. AMLOK confirms the unused balance and refund bank account and generates the final information. Workspace data is deleted after the request month closes and final information is generated.
4. **AMLOK issues an immediate refund of the entire unused credit balance when the account closes.** This includes promotional credits. Used credits are non-refundable.
5. Bank receipt can take **7-10 business days**, depending on the bank. Closure does not wait for delivery. Support or the enterprise account manager assists with a failed or returned refund.

The client portal provides these account controls. The public API provides reporting only, with no payment-setting, cancellation, refund, payout, approval, or transfer commands. See [cancellation and refunds](https://docs.amlok.io/pricing/refunds-and-payouts.md).

## Workspace retention and deletion

Authorized users configure retention in the AMLOK platform according to applicable compliance requirements. Cancellation includes workspace deletion; **when deletion is complete, all associated workspace data is deleted**. Disconnecting an individual integration is not an account cancellation.

See [privacy and data handling](https://docs.amlok.io/security/privacy.md) for retention and data scope.

AMLOK retains only the necessary final billing, refund, and bank-return records separately from the deleted workspace to reconcile the refund and resolve delivery issues. These records do not retain borrower source data, documents, or analysis outputs and do not keep the workspace or its API access active.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.