Troubleshooting

This page covers the most common issues merchants and developers may encounter when using Payment Channels, along with recommended resolution steps.

If you see unexpected behavior, review this page first before opening a support ticket.

Payment Links

Webhook for payment status is not received

If you do not receive a payment status webhook from PayMongo, such as link.payment.paid, checkout_session.payment.paid, or payment.paid, you can still verify the payment manually.

What to do

Use the payment_id associated with the transaction and call the Retrieve Payment endpoint to confirm the latest payment status:

GET /v1/payments/:id

For the full endpoint reference, see Retrieve a Payment.

When to use this workaround

Use this approach when:

  • a webhook has not been received yet
  • you need to confirm whether a customer payment was successful
  • you need a manual way to update payment status for Payment Links or Hosted Checkout

Important note

This is a temporary workaround for payment status verification. It can help you confirm and update the latest payment status for Links or Hosted Checkout flows, but it does not replace proper webhook handling.

If your issue is related to webhook delivery more broadly, refer to Troubleshooting Webhooks for further guidance.

Hosted Checkout

Expire a Checkout Session returns 400

The Expire endpoint refuses to expire a session in three cases: the session is already expired, the session has a paid payment, or the session has an ongoing payment.

What to do

Retrieve the session with the Retrieve a Checkout Session endpoint and check its status and payments.

  • If payments contains an entry with status: "paid", the customer paid. Fulfill the order.
  • If a payment is still in progress, wait for the checkout_session.payment.paid webhook, then retry the expiry if no payment arrives.
  • If status is already expired, no action is needed.

Do not create a new Checkout Session for the same order until the original session is confirmed expired.

A payment arrived for an expired or unknown session

A customer can save a QR Ph code before you expire the session. Most banking and e-wallet apps reject an expired code. If an app still sends the funds, PayMongo rejects the payment because the session's Payment Intent is cancelled. No payment is created, no checkout_session.payment.paid event is sent, and nothing appears in your Payments tab.

What to do

Ask the customer for the transaction reference from their banking or e-wallet app, then contact PayMongo support so the funds can be traced and returned. Do not fulfill the order from the customer's screenshot alone.

Customer reopened an old checkout URL

A Checkout Session stays active until you expire it. If the customer still has the URL and the session is active, they can pay on it. This is safe: a session can only produce one successful payment. If you no longer want the session to be payable, expire it. See Expiring a Checkout Session.



Did this page help you?