Stay organized with collections
Save and categorize content based on your preferences.
AI-generated Key Takeaways
Transaction statuses provide insight into the outcome of a purchase, such as success or failure.
Statuses like INVALID_PLAN_ID and PAYMENT_REQUIRED signal specific issues, like an incorrect plan selection or insufficient funds.
A CONFLICT status indicates incompatibility between the desired plan and the user's existing subscriptions.
Possible transaction statuses.
Enums
TRANSACTION_STATUS_UNSPECIFIED
The status of the transaction is unspecified.
SUCCESS
The transaction succeeded and details of the transaction are populated in transactionResponse.
INVALID_PLAN_ID
The purchased plan ID is invalid.
PAYMENT_REQUIRED
User does not have sufficient balance to complete the purchase.
CONFLICT
The plan to be purchased is incompatible with the user's current product mix. For example, if the operator data plan policy disallows mixing postpaid and prepaid plans, attempting to purchase a prepaid plan for a postpaid user will therefore lead to a CONFLICT.
[[["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 2023-10-03 UTC."],[],["Transaction statuses indicate outcomes. `SUCCESS` confirms a completed transaction with details in `transactionResponse`. `INVALID_PLAN_ID` means the plan is not valid. `PAYMENT_REQUIRED` denotes insufficient user balance. `CONFLICT` signals incompatibility between the requested plan and the user's existing setup, like mixing postpaid and prepaid plans when not permitted. `TRANSACTION_STATUS_UNSPECIFIED` represents an undefined status.\n"]]
