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. 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-02-28 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-02-28 UTC."],[[["\u003cp\u003eTransaction results are not yet determined and represented in JSON format.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003ereason\u003c/code\u003e field provides a code for why the transaction result is unknown.\u003c/p\u003e\n"],["\u003cp\u003eA common scenario for unknown results is when the debit is successful but the credit status is unknown, represented by the \u003ccode\u003ecreditStatusUnknown\u003c/code\u003e reason code.\u003c/p\u003e\n"]]],["The transaction result is currently unknown. The `reason` field explains why, which can only be `creditStatusUnknown`. This indicates that while the debit process was successful, the credit process is unknown. The `creditStatusUnknown` object type is defined as an `Empty` object. The `reason` field uses a union type to specify this single possibility.\n"],null,["# TransactionResultNotKnownYet\n\n- [JSON representation](#SCHEMA_REPRESENTATION)\n\nTransaction result not known yet.\n\n| JSON representation |\n|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| ``` { // Union field `reason` can be only one of the following: \"creditStatusUnknown\": { object (/pay/korea-e-wallets-v1/payment-integrator-korea-e-wallets-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/korea-e-wallets-v1/payment-integrator-korea-e-wallets-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. |"]]