Managing the Merchant Account

Open Merchant to review the signed-in merchant's company, address, contact, LHDN, submission, subscription, user, API client, and change-log information.

Confirm the merchant name and merchant code before making a change. Registration identifiers, submission preferences, and credentials can affect every outlet under the merchant.

Edit merchant information

  1. Open Merchant.
  2. Select Edit Merchant.
  3. Update the permitted company, contact, address, support, or status information.
  4. Select Apply Changes.

Review the TIN, BRN, business type, support contact, merchant status, and registered email carefully. Do not use another merchant's registration or contact details.

Maintain LHDN information

  1. Open Merchant.
  2. Select Edit LHDN Info.
  3. Review the TIN, BRN, SST, tourism tax, address, contact, country, state, MSIC, and submission preferences.
  4. Select TIN Validation to validate without saving, or TIN Validation & Save to validate and save.

Submission On (Hourly) and Consolidated On (Monthly) control the merchant's configured processing schedule. Change them only when the approved submission arrangement has changed.

If TIN validation fails, leave the information unsaved until the merchant identity and registration details have been checked.

Manage merchant users

To invite a user, select Add User, enter the login name, and select Send Invitation. The invited user must complete email verification before signing in.

To maintain an existing user, select the user from the account list, update the permitted details or active status, and select Apply Changes. Use Unregister User only when access should be removed.

Generate or replace an API credential

  1. Find the API Client section.
  2. Select Generate OAuth2 API Credential.
  3. Read the confirmation message and confirm only when every affected integration is ready for a replacement credential.
  4. Transfer the client information to authorized integration personnel using an approved secure method.

Client IDs and secrets grant system access. Never place them in documentation, screenshots, email, support tickets, or source code.

Regenerating the credential removes the existing API client. The old credential stops working, so every connected POS, retail, ERP, accounting system, or outlet integration must be updated and tested.

Review subscription information

The merchant information screen shows subscription and licensed-outlet information for reference. If the displayed period or outlet allowance is incorrect, contact the responsible reseller or AECloud Support.

Review account history

Use the change log to review recorded updates to the merchant account. The change log supports administrative review; it does not replace the merchant's own approval and audit procedures.