Testing Scenarios
Recommended scenarios to validate before launch.
Before going live, test the full Factoring Decline v1 flow from API submission to postback delivery.
Required test scenarios
| Scenario | What to verify |
|---|---|
| Valid API request | The API accepts a properly formatted request. |
| Missing API key | Requests without X-Api-Key are rejected. |
| Invalid API key | Requests with an invalid key are rejected. |
| Missing required field | The API returns a validation error. |
| Processor success | Your system records a successful payment result. |
| Processor decline | Your system records a failed payment result and stores the error message. |
| Postback success | Your endpoint receives the postback and returns HTTP 200. |
| Postback failure | A non-200 response appears in Postback Attempts. |
| Refund result | Refund postback is received and matched to the original transaction. |
Matching test
For every test order:
- Generate a unique
tracking2value. - Store it in your system as the merchant order reference.
- Submit the API request.
- Confirm the postback returns the same value as
clickID. - Update the same order record using
clickID,orderID, andtransactionID.
Portal checks
Confirm that:
| Page | Check |
|---|---|
| API Credentials | Both Live and Sandbox settings are visible: API URL, API Key, Campaign ID, Offer IDs, and Website ID. |
| API Settings | Postback URL and Statement Descriptor are configured separately for each website. Select a website to edit its API settings. |
| Postback Attempts | Test postbacks appear with request and response details. |
Updated 21 days ago
Did this page help you?