Skip to main content
Version: Current guides

Manage keys, Webhooks and integration testing

The current integration path​

Merchant routes for creating, retrieving, listing and closing Checkouts and listing payment methods are confirmed, subject to account and environment permissions. Confirm payments through server-side queries. Webhook endpoint management and delivery, payment details and refunds remain unconfirmed; settlement creation has separately unconfirmed execution support.

Public access to dashboard key management, event centers, simulators, sandbox resets and IP allowlists is unconfirmed. A visible menu or successful simulation does not establish production capability. Check exact requests and availability in the developer center's commercial payments documentation without using internal management interfaces.

Obtain, store and rotate credentials​

  1. Have an authorized owner obtain environment credentials through a verified onboarding route. If key creation is available, check its permissions and purpose first.
  2. Save the complete key directly to controlled server configuration, keeping it out of browser code, customer pages, source repositories and logs.
  3. Separate test and production credentials, resource IDs, notification endpoints and data. Do not infer permissions from a key prefix.
  4. Before rotation, confirm actual overlap and revocation rules. Prepare the replacement, test required retrieval and creation permissions, switch services and observe pending orders before revoking the old key as approved.
  5. For suspected exposure, prioritize incident revocation and recovery and investigate impact. Do not assume a fixed overlap period. Record actions without full secrets.

Confirm through queries first​

Before creation, save the order, attempt, parameters and idempotency key. Save the returned Checkout ID and actual URL afterward. Your server must retrieve only resources associated with its authorized merchant order, verify order, amount, currency, status and exception, then guarantee one fulfillment per order.

Keep unknown outcomes through timeouts, rate limits and restarts and recover original records. Use bounded frequency and backoff; browser loops or new collections do not replace recovery. See orders and exceptions.

Enable Webhooks after access is confirmed​

  1. Confirm both endpoint management and real delivery for the account and environment, along with signing, event and retry rules.
  2. Configure a server URL under the current contract, using HTTPS in production. Securely store the endpoint's complete secret; it is not the API Key.
  3. Capture raw request bytes before parsing JSON and verify Invisi-Signature under the current commercial payments specification. Do not automatically fall back to other signature-header names.
  4. After verification, persist the event and deduplicate by merchant, environment and event ID. Acknowledge reliable storage, then query related resources and process asynchronously.
  5. Retain Checkout query recovery and order-level fulfillment deduplication. Repeated, delayed or out-of-order events must not duplicate delivery. Successful delivery of a notification does not establish completed business handling.

For signature failures, inspect the endpoint secret, raw bytes, signature header and server clock. For missing events, query payment facts first; no notification does not mean unpaid.

Test before launch​

In an authorized test environment, rehearse normal payments, duplicate clicks, creation timeouts, failed retrievals, restarts, multiple successful Checkouts for one order, late funds, shortfalls, excess funds and forged browser success. Each outcome should remain recoverable, yield one order fulfillment and assign funds exceptions to an owner.

Add signature, duplicate and ordering tests only for enabled Webhooks; allowance and signing tests for enabled refunds; and rejection and post-send recovery tests for enabled settlements. Offline or simulated success does not prove real end-to-end access. Check whether the test environment uses on-chain transactions or assets with value rather than assuming a sandbox never moves funds.

For troubleshooting, provide environment, order or Checkout ID, time, available Request-Id and redacted errors. Exclude Authorization headers, full keys and token-bearing customer links.

Investigate with events and request logs​

Availability of dashboard event centers, request logs and resend tools remains unconfirmed. Where offered:

  1. Fix the account, environment, interval and business resource ID. Filter by supported type, event ID or related object and check that the environment and time filter are correct.
  2. Inspect event time, type, related resource and any supplied version information, then open the original order or funds task for its current outcome. An older event cannot override newer resource state.
  3. If delivery details exist, inspect endpoint, attempts, responses and errors separately. A generated event is not necessarily delivered, and HTTP success does not establish completed asynchronous business handling.
  4. Resend only when delivery and resend access are confirmed and the receiver supports signature verification and business deduplication. Verify the result. Resending recovers a notification; it does not create another payment, refund or fulfillment.
  5. Where request logs are available, trace results by request and resource identifiers. Confirm credentials are redacted before viewing or exporting. Preserve necessary evidence before using permitted log-management controls instead of clearing troubleshooting records first.

When events or logs are missing, recover payment facts through available Checkout queries, then check filters, permissions, record scope and tool availability. An empty list does not prove nonpayment. Do not integrate with unconfirmed event names or payloads.

Before using dashboard test tools​

Use only tools actually offered. First verify environment, credentials, whether test assets have value and whether simulation creates real tasks, on-chain transactions or real notifications. Checkout previews verify presentation, and simulated payments cover only documented simulator behavior. Neither replaces end-to-end acceptance in the target environment.

If notification simulation is offered, choose an authorized test endpoint and currently supported event structure without sending accidental events to production customer systems. Inspect delivery, signatures, persistence, resource retrieval and idempotent handling separately. Correct malformed custom data as instructed, without treating a simulated payload as the production contract. After a timeout inspect the original test task; after batches check orders for duplicate fulfillment and unresolved exceptions. Do not reset by erasing orders or logs still needed for review.