POST Payment checks — supplier_ref field is no longer required
Released: June 1, 2026
What changed
The supplier_ref field in the Payment Check API is no longer required. You can now submit a payment for evaluation without providing your internal supplier identifier.
Why it matters
Previously, if a payment was submitted without a supplier_ref, the API returned an error and the payment was not evaluated at all — meaning Trustpair could not assess it for fraud risk.
This was a common issue for integrations where payment data and vendor master data come from separate systems (such as an ERP and a dedicated supplier management system), and the internal supplier ID is not always available at the time the payment is processed.
With this change, payments without a supplier_ref are now accepted and evaluated. When this field is omitted, Trustpair will identify the right supplier record using the other identifiers included in the request.
What you need to do
Nothing, if you are already sending supplier_ref. Your integration will continue to work exactly as before.
If your system cannot always provide a supplier_ref, you can now remove it from your payload without causing errors. Make sure your payment request includes at least one of the following to allow proper matching: IBAN, registration number, or company name.
Behavior summary
| Scenario | Before | After |
|---|---|---|
Payment submitted without supplier_ref, with registration number | ❌ Rejected — payment not evaluated | ✅ Accepted — evaluated |
Payment submitted without supplier_ref, with company name only | ❌ Rejected — payment not evaluated | ✅ Accepted — evaluated |
Payment submitted with supplier_ref | ✅ Evaluated as usual | ✅ No change |
Notes
- This is a non-breaking change. No updates to your API credentials or configuration are needed.
- Sending
supplier_refwhen available is still recommended — it remains the most direct and reliable way to match a payment to a supplier record.