Update Transaction
Overview
You can update a transaction by adding or modifying non-mandatory fields while it is in SCHEDULED or PENDING status. The update is performed with a POST request to the transaction’s ID or external ID endpoint.
Notes
• Once scheduled,sourceanddestinationcannot be changed. Cancel and create a new transaction instead.
• Transactions of typeREFUNDcannot be updated.
Resource Access
Production (api.ahrvo.network)
POST https://api.ahrvo.network/banking/us2/v1/transaction/id/{transactionId}
Staging (gateway.ahrvo.network)
POST https://gateway.ahrvo.network/banking/us2/v1/transaction/id/{transactionId}
Arguments — Top-Level
| Attribute | Can Be Updated? |
|---|---|
externalId | Conditional – once set, cannot be changed |
source / destination | No |
type / method | No |
amount, currency | Yes |
scheduleDate | No |
allowDuplicate, purpose | Yes |
linkedSchedule, linkedDocument | Yes |
comment, metadata, tags | Yes |
Arguments — processingDetail Nodes
| Method | Node | Updatable? |
|---|---|---|
| ACH | processingMode, companyName, companyDescription, authType, addenda | Yes |
quickSettle | No | |
| WIRE | memo | Yes |
| CARD | statementDescriptor | Yes |
merchant.id, merchant.externalId | No | |
| CHECK | deliveryMode, remittanceInfo, memo | Yes |
checkType, routingNumber, onUs, auxiliaryOnUs, quickSettle | No | |
| REFUND | achRefundCompanyName, achRefundCompanyDescription, statementDescriptor | Yes |
parent | No | |
| BOOK | purpose, memo | Yes |
| INTERNATIONAL_WIRE | memo | Optional (Y) |
| VIRTUAL_CARD | virtualCard.cardProgram.id, virtualCard.nickname, virtualCard.entity.id | No |
Nodes marked Yes (or Y) can be updated.
Example — Update Amount
POST /v1/transaction/id/2554
{
"amount": "500.50"
}
Response
HTTP/1.1 204 No Content