confirmPayment

If a payment request (createPayment operation) is successful, and returns a 201 status, it must be confirmed or cancelled in order to complete the transaction. Confirmation of a payment (this operation) will only succeed if the payment was previously created, but not cancelled. This operation must be repeated until a final HTTP status code is received (i.e. 202 or 400). If a 5xx status code is received, or no response is received, the request must be repeated. The confirmation operation is idempotent and may be called repeatedly on the same payment resource without adverse effect.

SecurityhttpBasic

Request

path Parameters

adviceId required	string The randomly generated UUID of this request
paymentId required	string The UUID generated for the original `createPayment` request

Request Body schema: application/json

A payment confirmation

id required	string The randomly generated UUID identifying this advice, as defined for a variant 4 UUID in RFC 4122
requestId required	string The UUID identifying the request that this advice relates to
time required	string <date-time> The date and time of the message as recorded by the sender. The format shall be as defined for date-time in RFC 3339 section 5.6. It is recommended that the optional time-secfrac be included up to millisecond precision
required	Array of objects (ThirdPartyIdentifier) The unaltered thirdPartyIdentifiers array as supplied in the related BasicResponse message. Required if thirdPartyIdentifiers field was present in the BasicResponse. If no thirdPartyIdentifiers was received in the BasicResponse or no BasicResponse was received then this should be set to the thirdPartyIdentifiers sent in the original request.
stan	string The System Trace Audit Number can be used to locate transactions across different systems.
rrn	string This is a reference set by the original source of the transaction.
	object (Amounts) Amounts which make up the transaction. Absent amounts have zero value.
required	Array of objects (Tender) An array of tenders used to pay for the transaction

Responses

202

Accepted

400

Bad request

500

Internal server error

503

Service unavailable

504

Gateway timeout

post/payments/{paymentId}/confirmations/{adviceId}

Request samples

Payload
curl
Java
Node.js

application/json

{"id": "string",
"requestId": "string",
"time": "2019-08-24T14:15:22Z",
"thirdPartyIdentifiers": [{"institutionId": "string",
"transactionIdentifier": "string"
}
],
"stan": "string",
"rrn": "string",
"amounts": {"requestAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"approvedAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"feeAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"balanceAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"additionalAmounts": {"property1": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"property2": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
}
}
},
"tenders": [{"accountType": "DEFAULT",
"amount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"cardNumber": "string",
"reference": "string",
"tenderType": "CASH"
}
]
}

Response samples

application/json

{"id": "string",
"requestId": "string",
"time": "2019-08-24T14:15:22Z",
"thirdPartyIdentifiers": [{"institutionId": "string",
"transactionIdentifier": "string"
}
],
"stan": "string",
"rrn": "string",
"amounts": {"requestAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"approvedAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"feeAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"balanceAmount": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"additionalAmounts": {"property1": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
},
"property2": {"amount": 0,
"currency": "string",
"ledgerIndicator": "DEBIT"
}
}
}
}