Use this checklist before moving a Factoring Decline v1 integration to production traffic.
| Check | Required |
|---|
| Merchant portal access is active. | Yes |
| Compliance is submitted and approved. | Yes |
| API Credentials are visible. | Yes |
| API Settings are configured. | Yes |
| Statement Descriptor is set. | Yes |
| Postback URL is configured. | Recommended |
| Check | Required |
|---|
| Requests are sent from a secure server-side environment. | Yes |
X-Api-Key is stored securely. | Yes |
campaign_id, offer_id, and tracking1 are copied from the portal. | Yes |
tracking2 is unique per submitted order. | Yes |
| Customer and payment fields are validated before submission. | Yes |
| API responses are stored for reconciliation. | Yes |
| Check | Required |
|---|
Endpoint accepts POST requests. | Yes |
| Endpoint accepts JSON. | Yes |
| Endpoint uses HTTPS. | Yes |
Endpoint returns HTTP 200 after successful receipt. | Yes |
| Endpoint responds within 30 seconds. | Yes |
| Failed deliveries can be reviewed in Postback Attempts. | Yes |
| Check | Required |
|---|
tracking2 is stored before API submission. | Yes |
Incoming clickID is matched to the original order. | Yes |
orderID and transactionID are stored after response or postback. | Yes |
success, failed, processing, and refunded statuses are handled. | Yes |
| Refunds update the original transaction record. | Yes |
Before launch, run at least one end-to-end test covering:
- API request submission.
- API response handling.
- Postback delivery.
- Postback matching by
clickID.
- Failed postback troubleshooting.
- Refund result handling.
