TransactionResultNotKnownYet
Stay organized with collections
Save and categorize content based on your preferences.
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. REQUIRED: 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 2025-07-29 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-29 UTC."],[[["\u003cp\u003eThe JSON response provides details about the reason for an unknown transaction result.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ereason\u003c/code\u003e field can have the value \u003ccode\u003ecreditStatusUnknown\u003c/code\u003e, indicating the credit leg of a real-time payment is unknown while the debit leg is successful.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003ecreditStatusUnknown\u003c/code\u003e is represented by an empty object, signaling a lack of specific details regarding the unknown credit status.\u003c/p\u003e\n"]]],["The content defines the `reason` field within a JSON structure, which indicates why a transaction's result is unknown. The `reason` field can only be one of the specified types. Currently, the only defined type is `creditStatusUnknown`, which is an object of type `Empty`. This specific type signifies that while the debit portion of the transaction was successful, the credit portion's status remains unknown, a common scenario in real-time payment systems.\n"],null,["- [JSON representation](#SCHEMA_REPRESENTATION)\n\n| JSON representation |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ``` { // Union field `reason` can be only one of the following: \"creditStatusUnknown\": { object (/pay/banking-fop-v2/payment-integrator-banking-fop-api/Empty) } // End of list of possible types for union field `reason`. } ``` |\n\n| Fields ||\n|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Union field `reason`. Code specifying the reason behind the transaction result not being known. `reason` can be only one of the following: ||\n| `creditStatusUnknown` | `object (`[Empty](/pay/banking-fop-v2/payment-integrator-banking-fop-api/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. |"]]