Skip to main content
  • Trigger – Supplier Payment run created in ERP
  • Cadence – Per run or daily.
  • Mode – Asynchronus / Poll
  • Product – Inyett Payment Control

​
Process

​
Step by step

  1. Export the pending payment run from your ERP
  2. Submit the whole batch with your own external IDs.
    POST /2/{pc}/payment-control/batches
  3. Receive 200 — Accepted, not analysed
  4. Poll every 2 – 3 seconds until the status settles.
    GET /2/{pc}/payment-control/batches/{externalBatchId}/warnings
  5. On Done, map warnings back by TransactionExternalId
  6. Hold flagged rows, release the rest to the bank.
  7. If the run is cancelled upstream, revoke the batch.
    DELETE /2/{pc}/payment-control/batches/{externalBatchId}
The single most common integration bug is treating the POST response as the result. A 200 means accepted for analysis. Read warnings immediately and you will get an empty list and wrongly release a fraudulent payment.