- REST APIs
- Welcome
- Card Payments
- 3D Secure 2
- Vault
- Getting Started
- Using the API
- Typical API Calls
- Verify That the Service Is Accessible
- Create a Profile for a Customer
- Add an Address to a Profile
- Add a Card to a Profile
- Add a Bank Account to a Profile
- Create an Apple Pay Single-Use Token
- Create a Google Pay Single-Use Token
- Create a Mobile Single-Use Token
- Create a Direct Debit Single-Use Token
- Process a Transaction Using a Payment Token
- API Reference
- Test and Go Live
- Direct Debit
- Apple Pay
- Google Pay
- Business Portal
- Partner Portal
- Alternate Payments
- Reports API
- ISV Reports
- Platforms
- Overview
- Accounts API V1
- Getting Started
- Using the API
- Typical API Calls
- Verify That the Service Is Accessible
- Create a New Merchant
- Create a New Merchant Account
- Create a New User
- Add an Address
- Create a Business Owner
- Add a Business Owner Address
- Add a Business Owner Identity Document
- Add a Merchant Bank Account
- Accept Our Terms and Conditions
- Activate the New Merchant Account
- Validate the Bank Account
- Enable Webhooks to Receive Application Statuses
- Test and Go Live
- Subaccounts
- Applications API
- Split Payouts
- Balance Transfers
- Paysafe Payments API
- Paysafe Checkout
- Paysafe JS
- Payments API
- Bad Bin API
- Reference Information
- SDKs
- Mobile SDKs
- Additional Documentation
- Resources and Support
- Shopping Carts
- Classic APIs
- Glossary
Test Environment
This document describes the events that can be tested / not tested in test environment. Below is the list of webhooks that can be tested if the following pre-requisites are available:
-
Merchant/Partner must have a subscription with Netbanx to test all events.
-
Merchant/Partner must have webhook payloads for all schemas (ACH, EFT, BACS, and SEPA) to test in Netbanx.
| S.No. | EventName | Events that can be tested in Sandbox | Comments | |||
|---|---|---|---|---|---|---|
| ACH | EFT | BACS | SEPA | |||
| 1 | Payment_Completed | Yes | Yes | Yes | Yes | For BACS Mandate will be activated. With Active Mandate only we can create purchase call. |
| 2 | Settlement_Cleared | Yes | Yes | Yes | Yes | |
| 3 | Settlement_Cancelled | Yes | Yes | Yes | Yes | |
| 4 | Payment_Return_Completed | Yes | Yes | Yes | Yes | |
| 6 | Settlement_Completed | Yes | Yes | Yes | Yes | This event will trigger when you move the transaction status to payment_returned in portal. |
| 7 | Payment_Failed | Yes | Yes | Yes | Yes | |
| 10 | Settlement_Pending | Yes | Yes | Yes | Yes | This is part of the Payment_Completed event only. There will be no separate event for Settlement_pending. |
| 11 | StandAloneCredit_Pending | Yes | Yes | Yes | NA | |
| 12 | StandAloneCredit_Completed | Yes | Yes | Yes | NA | |
| 13 | StandAloneCredit_Return_Completed | Yes | Yes | Yes | NA | |
| 14 | StandAloneCredit_Failed | Yes | Yes | Yes | NA | |
| 15 | StandAloneCredit_Cancelled | Yes | Yes | Yes | NA | |
| 16 | StandAloneCredit_Processing | NA | NA | NA | NA | |