Troubleshoot Payment Status & Webhooks
Diagnose authorization, signature, event, duplicate, amount, currency, pending, and activation problems.
Overview
Payment succeeds but Wemblo stays Pending: Check provider delivery log, endpoint, event type, signature, and environment.
Unauthorized: Check key, account, and test or live mode.
Duplicate transaction: Check event ID and idempotency.
Wrong amount: Check currency, fee, tax, deposit, and mapped record.
Activation occurs too early: Require verified server-side payment status.
Who should use it
Workspace owners, operations teams, sales users and authorized technical users.
Where to find it in Wemblo
Wemblo -> My Subscription -> Payment Gateway / Payment Transactions
Before you begin
- Use the correct workspace and authorized role.
- Prepare fictional Pakistan test data.
- Confirm connected provider accounts where required.
- Define who approves price, stock, booking, payment or final status.
Main concepts and fields
| Concept / Field | Meaning or Use |
|---|---|
| Endpoint | HTTPS URL receiving an event. |
| Authentication | Key or secret protecting the request. |
| Event ID | Unique event reference. |
| Idempotency | Prevents duplicate processing. |
| Mapping | Connects event data to Wemblo fields. |
Step-by-step instructions
- Record the workspace, user, module, time in PKT and exact error.
- Confirm the correct role, workspace and active connection.
- Review status, usage and recent configuration changes.
- Reproduce with fictional data.
- Review logs or provider response.
- Correct one issue at a time and retest.
- Escalate with redacted evidence if unresolved.
Test and verification
- Complete one successful path with fictional data.
- Complete one invalid, failure or permission path.
- Confirm the result appears in the correct workspace and module.
- Confirm the correct person or team can review and continue the work.
Common issues and solutions
| Issue | What to Check |
|---|---|
| Configuration does not save | Required fields, validation, permission and active workspace. |
| External action fails | Credential, provider status, endpoint or field mapping. |
| Duplicate record or action | Event ID, idempotency, retries and existing record. |
| Customer notification is missing | Template, channel connection, status transition and contact details. |
Security, privacy, consent, cost and provider notes
- Use only data the business is authorized to process.
- External provider charges, policies, approvals, limits and availability remain separate.
- Do not expose passwords, API keys, tokens, webhook secrets, payment credentials or private customer data.
- Use human review for sensitive, regulated, urgent, financial or final decisions.
Last reviewed: