TransactionResultNotKnownYet
Transaction result not known yet.
| JSON representation |
{
// Union field reason can be only one of the following:
"creditStatusUnknown": {
object (Empty)
}
// End of list of possible types for union field reason.
} |
| Fields |
Union field reason. Code specifying the reason behind the transaction result not being known. reason can be only one of the following: |
creditStatusUnknown |
object (Empty)
Credit status unknown. This is one of the common scenarios where a transaction is unknown in a real time payment system when debit leg is successful but the credit leg is unknown.
|
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-22 UTC.
[null,null,["Last updated 2024-10-22 UTC."],[[["Transaction result is currently unknown, often due to successful debit but pending credit in real-time payment systems."],["The API response uses a JSON schema with a \"reason\" field indicating the cause of the unknown status."],["When the reason is \"creditStatusUnknown,\" it signifies that the credit leg of the transaction is still pending while the debit leg was successful."],["This scenario is common in real-time payments where the credit status might not be immediately available."],["An \"Empty\" object is used as a placeholder for additional information when the credit status is unknown."]]],["The document describes a scenario where a transaction's result is unknown. This is represented in JSON with a union field named `reason`. The only defined possibility for `reason` is `creditStatusUnknown`, which indicates the credit status of the transaction is unknown. This situation commonly occurs when the debit part of the transaction succeeds, but the credit aspect is not yet confirmed within a real-time payment system. An `object` called `Empty` refers to this `creditStatusUnknown`.\n"]]