Skip to main content
Monitoring starts with identifiers. Store the Payment Intent ID alongside your order and log webhook event IDs in your receiver. Those values connect your application records to Lynq Dashboard without exposing credentials.

​
Monitor payments

Use Dashboard → Payments in the appropriate environment to review:
  • Payment Intent ID and merchant orderId
  • Amount and currency
  • Payment status
  • Card brand and last four digits or Idram method summary
  • Payment attempt history and last payment error
  • Creation and update time
When a customer contacts support, start with the merchant order ID, then find the corresponding Payment Intent. Do not ask the customer for full card details or provider credentials.

​
Monitor webhook delivery

Use Dashboard → Webhooks to inspect endpoint health and individual deliveries. Delivery details include the event ID, type, source, attempt count, latest HTTP status, last error, and timestamps.

​
Investigation playbook

Find the Payment Intent in Dashboard, then inspect its webhook delivery. If delivery succeeded, search receiver logs by event ID and confirm the order comparison and database transaction. If delivery is retrying, restore the endpoint and let Lynq retry.
Check the latest HTTP status or network error. 408, 429, 5xx, timeouts, and connection failures are temporary. Fix the receiver without changing the endpoint URL unless necessary.
Check for an unsafe or unreachable destination and non-retryable 4xx responses. Confirm the URL is public HTTPS and the receiver is not returning authentication errors for valid signatures.
Confirm the receiver uses the raw body and the current environment’s signing secret. If the secret was rotated, requests immediately use the new value.
Check the Payment Intent environment, publishable key environment, and enabled payment methods. Then confirm the provider credentials were saved in that same environment.

​
Credential incidents

If a secret API key is exposed, create a replacement, update every server that uses it, verify the deployment, and revoke the old key. If a webhook signing secret is exposed, coordinate an immediate rotation because verification switches to the new secret as soon as you rotate it. For help, contact support@lynq.am with the environment, Payment Intent or event ID, approximate time, and observed error. Never include secret values.
Last modified on August 8, 2026