Callback Payment Request

The merchant needs to have an endpoint available where Tinka can send an update of the payment request. The message below is sent to this endpoint in JSON format with a HTTP POST request. The payload is the same as the response for the status request. The request will be signed in the same way a response of a synchronous call is signed. The signature will be sent via a HTTP header: X-Authorization: hmac <hash>:<nonce>:<timestamp> for more information see security.

Request

Attribute	Type	Length	Description
`paymentRequestId` required	String	36	A unique number for this payment request transaction. It`s a UUID
`paymentMethod` required	String	2000	The original payment method. Can be used for extra verification on the merchant's side
`requestedPaymentAmount` required	Integer		The original requested amount in euro cents. Can be used for extra verification on the merchant's side
`decision` required	Enum String		The decision of the paymentRequest. See decision
`decisionDateTime` required	String		Date of the decision. Format `yyyy-mm-ddThh:mi:ss.SSSZ` In UTC timezone. Example: `2018-11-06T09:41:25.020Z`
`transactionId` required	String	100	A reference provided by the caller. Can be used for extra verification on the merchant's side
`merchantRequestReference` required	String	100	A unique reference provided by the merchant. Can be used for extra verification on the merchant's side
`errorCode`	String		Error code (indication of the nature of the error). List of error codes needs to be decided
`additionalData`	String	255	Additional info for the payment request. Possibly a reject reason or error message

Example

Response

{
  paymentRequestId: '01234567-aaaa-bbbb-cccc-987654321abc',
  paymentMethod: 'Credit',
  requestedPaymentAmount: 90000,
  decision: 'Accepted'
  decisionDateTime: '2020-02-02T09:40:00.020Z',
  transactionId: 'unique-xxxxxxxxxxxxxxxxxxxx',
  merchantRequestReference: 'xxxxxxxxxxxxxxxx'
}