Connect a Supported Payment Gateway
Connect a currently supported payment provider using business-owned test and production credentials.
STEPS
- Confirm the gateway is supported in the current Wemblo release.
- Create and verify the provider business account.
- Create test credentials.
- Open Wemblo Payment Integrations and select the provider.
- Enter credentials only in protected fields.
- Configure the webhook.
- Test success, pending, failed, duplicate, and refund cases.
- Move to live credentials only after approval.
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 |
|---|---|
| Gateway | External payment provider. |
| Public Key / Merchant ID | Provider identifier. |
| Secret Key | Private server credential. |
| Webhook Secret | Verifies payment events. |
| Transaction Status | Pending, paid, failed, refunded or other provider state. |
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: