Skip to main content
Version: Current guides

Team and security

Availability​

Use credential protection and incident handling here as internal operating procedures. Dashboard controls for 2FA, Passkeys, devices, IP allowlists, audit logs and teams remain unconfirmed. Configure them only when offered; no fixed lockout duration, recovery-code count or log retention is promised.

Protect routine operations​

  1. Give each member an individual account instead of sharing the owner's password. Divide order, support, funds and integration duties using team access.
  2. Sign in through a verified merchant entry. If two-factor authentication is offered, complete setup and store recovery materials securely. Do not share setup QR codes, verification codes or recovery codes.
  3. Store API Keys and notification signing secrets only in controlled server storage. Separate test and production; exclude full credentials from logs, browser code and screenshots.
  4. Have another responsible person check the network, full wallet address and purpose before payment configuration changes. Inspect the current task before signing, rather than relying on a wallet prompt title.
  5. Regularly review members, credentials and available device records. Offboarding must also cover wallet signing rights and external systems.

Recover passwords or verification access​

Start recovery from the verified sign-in page and complete the email and applicable secondary checks it provides. Use saved recovery codes only if supported. Check device time when an authenticator fails. If both the device and recovery materials are lost, request account recovery through your verified onboarding contact rather than bypassing checks.

Do not repeatedly guess codes; follow the displayed wait or reissue instructions. A password reset does not recover a wallet or establish that old API Keys are invalid. Check those permissions separately after recovery.

Suspected account or key compromise​

  1. Preserve the time, members involved, order or Checkout IDs, errors and available audit records without exposing full credentials.
  2. Where supported and authorized, revoke suspicious credentials and remove unknown access. Pause affected payment-configuration changes and notify your internal owner.
  3. Deploy replacement credentials using the developer guide and verify queries recover. Review pending orders across the change to avoid missed fulfillment.
  4. Check for wallet changes and already-submitted refund or settlement transactions. If a transaction was sent but its outcome is unknown, inspect the original task before signing another transfer.
  5. Share redacted records through a verified channel and confirm impact and recovery conditions with your contact. Retain the incident record and review member access afterward.

If dashboard controls are unavailable, have the account owner coordinate supported recovery measures with the contact. Missing dashboard records do not establish that no funds operation occurred.

Branding, networks and risk settings​

Public availability of branding, custom domains, email templates, notification preferences, network settings and risk rules remains unconfirmed. Use these steps only for screens actually offered. Automatic certificates, white-label plans and a live rule engine are not promised.

Check customer-facing branding​

  1. Prepare the public merchant name, logo, contact details and readable colors, using assets you have rights to use.
  2. Save and preview supported Checkout, invoice or email contexts. Check text contrast and mobile readability.
  3. If domain or sender configuration is enabled, copy only DNS records supplied by the current screen and complete ownership verification. Use current verification results to establish activation.
  4. Test actual customer entries and notifications, verifying links, display names and support contacts. A successful preview does not establish domain activation or email delivery.

Change networks and assets​

Inspect available payment combinations, wallets and unresolved orders before enabling or disabling anything. After saving, verify methods on new Checkouts and separately track old sessions and bound settlements. Configuration changes do not establish funds migration, closure of old sessions or replacement of task wallets. If no configuration screen exists, ask your contact instead of calling internal configuration interfaces.

Adjust risk rules and notifications​

Define which new business requests should be recorded, reviewed or rejected. If enabled rules support observation, test a small set of scenarios, inspect matches and false positives, then switch to blocking only as approved. Verify actions and scope rather than assuming review timeouts automatically approve or reject. For false positives, inspect rules and order facts before recovery; a rule label does not invalidate payment by itself.

Configure a reachable email or channel only where offered and test delivery. Operational alerts, payment state and Webhooks are distinct. Disabling alerts does not cancel payments, and fulfillment must not depend on email arrival. Retain the operator, time and review result for rule and setting changes.

Edit customer email templates​

Only when template management is enabled, select the correct event and language template and preserve the original before editing subject and body. Insert only variables offered by the current editor and check links, amounts, currencies and customer names. Exclude private information and credentials.

If previews and test delivery are offered, inspect sample values, mobile layout and branding, then send to an authorized mailbox and verify real links. A preview does not establish correct production fields or delivery. Save and reload after approval rather than only previewing. Correct invalid variables or empty fields according to current validation without relying on automatic default-body fallback.

Before toggling a template, inspect the customer-notification effect. Disabling it does not cancel transactions or replace subscription or email-preference management. Preserve needed edits before restoring defaults and test afterward. For failed tests, inspect the address, send status and template rather than repeatedly mailing customers in bulk.

Review transactions awaiting a decision​

Only where risk records and review operations are enabled:

  1. Locate the triggering rule, time, order and actual action. Distinguish observation, blocking and pending review rather than relying on a risk label.
  2. Open the original order and authoritative payment result and inspect the amount, association and existing payment or fulfillment. Approval cannot change an on-chain fact.
  3. Have an authorized reviewer approve or reject using current business evidence and record a reason. Reload the decision and original order before deciding whether to resume work.
  4. For a timeout, stale page or another operator's decision, refresh first rather than repeatedly submitting opposing decisions. Preserve rule matches and final transaction outcomes separately.

Verify actual timeout behavior for the account without promising automatic approval or rejection. Corporate-card spending has separate limits and approvals; merchant payment risk rules do not necessarily apply to it.