Confirm Payment (UTR)

POST/v1/h2h/buyer-confirms-paymentpayin:create

After the customer completes the UPI payment in their bank app, they receive a UTR (Unique Transaction Reference). Collect it on your payment screen and submit it to Transacty so the trade can be verified and settled.

Request fields

Field	Type	Required	Description
`transactionId`	`string`	Yes	`transactionId` from the create response
`utr`	`string`	Yes	Bank UTR / reference the customer received after paying

Example

Request


{
  "transactionId": "d562be7c-00d4-4d63-bf50-93f72b437222",
  "utr": "401312345678"
}

cURL

curl -X POST https://api.transacty.ai/v1/h2h/buyer-confirms-payment \
  -H "X-Transacty-Key: $TRANSACTY_KEY" \
  -H "X-Transacty-Timestamp: $TS" \
  -H "X-Transacty-Signature: $SIG" \
  -H "Content-Type: application/json" \
  -d '{
  "transactionId": "d562be7c-00d4-4d63-bf50-93f72b437222",
  "utr": "401312345678"
}'

Response


{
  "transactionId": "d562be7c-00d4-4d63-bf50-93f72b437222",
  "status": "pending",
  "acknowledged": true
}

Response fields

Field	Type	Description
`transactionId`	`string`	Echoes the confirmed transaction
`status`	`string`	Typically still `pending` while verifying
`acknowledged`	`boolean`	`true` when the UTR was accepted for verification

Submitting the UTR does not immediately mark the trade as successful. A wrong UTR may move the trade into dispute (trade event 5); operations may correct and complete it as event 4 without the merchant resubmitting. Do not treat dispute as a final failure in your UI copy. The wallet is credited only on a completion event (4 or 6).

Track progress via Pay-in Status & Events or webhooks.