Payment executions

Report a payment you made to a counterparty after a decision.

Records what you actually paid your counterparty following a decision, so the verdict and its consequence can be read together later.

This is not a payment to Fidren. It is the payment the decision was about.

Idempotent on client_reference within your organization: reporting the same reference twice answers 200 rather than creating a second execution, so a retry is safe. Unknown fields are rejected rather than ignored — in particular you cannot record that your own payment was seen on chain. Reporting that you sent money is a statement about what you did; whether it arrived is something Fidren records only from its own reading of the chain.

Attaching operation_id points at the receipts chain. It says nothing about what the counterparty then did — that is what receipts are for, and both sides report there.

post/v1/payment-executions

Request

  • Base URL: https://api.fidren.net
  • URL: https://api.fidren.net/v1/payment-executions
  • Auth: one of:
    • HTTP bearer
    • API key in header X-API-Key

Request body

decision_idstring required
client_referencestring required

Your own identifier for this execution. Unique within your organization, and what makes reporting idempotent.

amount_centsinteger required

What you actually paid, which may differ from what you asked about.

currencystring
reported_executed_atstring date-time required

When you say the payment was sent. Recorded as your claim.

operation_idstring

The commercial operation, if you already know it. Optional, and says nothing about what the counterparty then did.

Response

Already recorded under this client_reference. A retry.

Changes

No recorded changes to this operation across all 1 revision of this API.