confirmTokenPurchase

Confirms that a purchase has been completed successfully (i.e. the tokens have been issued to the customer and payment has been received by the merchant). It is typical that token providers do not support confirmations (aka advices), but certain point-of-sale integrations may require support for these. A confirmation request must be sent repeatedly until an HTTP response code indicating a final state has been received (i.e. either 202 or 4xx).

SecurityhttpBasic or oauth2

Request

path Parameters

purchaseId required	string The randomly generated UUID of the original purchase request.
confirmationId required	string The randomly generated UUID of this confirmation.

Request Body schema: application/json

A token purchase 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

404

Not found

500

Internal server error

501

Not implemented

503

Service unavailable

504

Gateway timeout

post/tokenPurchases/{purchaseId}/confirmations/{confirmationId}

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"
}
}
}
}