When a payment fails or encounters an issue, use the following steps to diagnose the problem.
Checking payment status in the Dashboard
- Log in to the Flinks Dashboard.
- Navigate to Payments.
- Click the Error tab to view failed payments.
- Select a payment to view its details, including the
paymentStatus and statusDetails fields.
Checking payment status via API
Use the /PaymentRequests GET endpoint to check the status of a payment:
curl -X GET \
https://{baseurl}/api/v1/paymentrequests/{requestId} \
-H 'Authorization: Bearer {access_token}' \
-H 'BaseURI: {instance}'
Payment status reference
| Status | Description |
|---|
Initiated | Payment request received and ready for processing |
Processing | User is completing the transaction |
Accepted | User accepted the payment; funds flow has started (funds guaranteed) |
Processed | Transaction processed; awaiting settlement |
Settled | Funds transfer completed to your account |
Cancelled | Payment cancelled before being initiated |
Expired | User did not action the request in time |
Declined | User declined the payment at their financial institution |
Failed | Payment request failed (check statusDetails for reason) |
- Open your browser’s Developer Tools (F12 or Ctrl+Shift+I).
- Go to the Network tab.
- Search for
SearchLiveTransactionHistories in the network requests.
- Inspect the response to find the
paymentStatus and statusDetails fields.
EFT return codes
EFT transactions can fail with a Payments Canada return code (CPA005 standard, plus Rule H1 codes for PAD disputes). Each code maps to a specific operational decision: cancel the schedule, contact the user, review before acting, or escalate.
See the EFT Failure Scenarios playbook for the full list of codes, what each one means, the impact on your schedule, and the exact next steps to take.
Any return code flagged as a PAD Dispute triggers an automatic recall of funds while the dispute is under review. Contact Flinks Payments Support immediately — do not wait.
Common issues
| Problem | Possible cause | Solution |
|---|
Payment stuck in Processing | User hasn’t completed the flow | Follow up with the customer or check if the session expired |
Failed with failed_name_matching | Name mismatch between session and bank | Create a new session with the correct name |
Payment Expired | User didn’t action the e-transfer request | Initiate a new payment request |
| EFT return code | Bank rejected the EFT transaction | Look up the code in EFT Failure Scenarios and follow the decision (cancel, retry, review, or escalate) |
