Sign in

v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB
Payments (Pismo account ID)

Confirm payment (Pismo account ID)

Confirm an existing payment operation.

NOTE:

See Data and reporting for more information on events and setting up event notifications.

post/cash-management/v2/payments/confirm

Request body

original_tracking_idstring required

Tracking ID for the original operation.

tracking_idstring required

Customer created tracking ID. Must consist of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and colons (:), with a length from 1 to 128. The Pismo platform uses this field to implement idempotency and prevent duplicates.

business_datestring date

Specifying a business_date value impacts the account balance history.<br> <b>Notes</b>:

  • The business date is in ISO 8601 format.
  • The business date allows users to designate the balance history cycle in which a payment is posted.
  • You can specify a business_date within the current working day or up to one working day before or after.
skip_account_date_validationboolean

If FALSE, the payment_datetime is validated against the account creation date and time. If TRUE, the validation is skipped.

metadataConfirmPaymentMetadata

Key-value pairs containing data intended for storage in the Pismo system.<br>

Note: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to Get started with Pismo APIs.

Example request

{
  "original_tracking_id": "249fbd1c-cfcd-48aa-8bcb-1ffe3a5f7978",
  "tracking_id": "3368328d-e4c6-4c75-99a9-9d59f3501d8c",
  "business_date": "2023-03-09"
}

Response

Created

original_tracking_idstring

Tracking ID for the original operation.

tracking_idstring

Customer created tracking ID. Must consist of alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and colons (:), with a length from 1 to 128. The Pismo platform uses this field to implement idempotency and prevent duplicates.

event_datetimestring date-time

Event date and time displayed in ISO 8601 format.<br> minLength: 1 maxLength: 30

Example response

{
  "original_tracking_id": "249fbd1c-cfcd-48aa-8bcb-1ffe3a5f7978",
  "tracking_id": "3368328d-e4c6-4c75-99a9-9d59f3501d8c",
  "event_datetime": "2023-04-27T12:01:24Z"
}