When a transaction posts, the transition from a pending to posted transaction will be represented through the /transactions/sync endpoint with the pending transaction's id in the removed field of the response and the new posted transaction in the added section of the response - note that these aren't guaranteed to be in the same page, but should happen within the same overall update. This is why it's important to apply all modified, added, and removed updates surfaced through /transactions/sync in order to maintain consistency with the underlying account data. For example, a refund or a recategorization of a transaction by the institution could cause a previously posted transaction to change. Note that while transactions will rarely change once they have posted, a posted transaction cannot necessarily be considered immutable. Pending transactions are short-lived and frequently altered or removed by the institution before finally settling as a posted transaction. In some cases, a pending transaction may not convert to a posted transaction at all and will simply disappear this can happen, for example, if the pending transaction was used as an "authorization hold," which is a sort of a deposit for a potential future transaction, frequently used by gas stations, hotels, and rental-car companies. For example, the pending charge for a meal at a restaurant may not include a tip, but the posted version will include the final amount spent, including the tip. The pending and posted versions of a transaction may not necessarily share the same details: their name and amount may change.
It typically takes about one to five business days for a transaction to move from pending to posted, although it can take up to fourteen days in rare situations.
A transaction begins its life as a pending transaction, then becomes posted once the funds have actually been transferred. There are two types of transactions: pending and posted.
0 kommentar(er)
