Configure Payment Webhooks
Configure provider payment events, signature verification, transaction mapping, retries, and duplicate protection.
STEPS
- Copy the Wemblo payment webhook URL.
- Open the provider's webhook settings.
- Create the endpoint and select required payment events.
- Create or copy the webhook secret.
- Enter the secret in Wemblo.
- Send a provider test event.
- Confirm signature verification and transaction update.
- Confirm duplicate events do not create duplicate orders or activations.
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. |
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: