> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/products/tmedia/features-and-solutions/solutions/prepaid-and-postpaid-calling.md). # Prepaid & postpaid calling According to [Ezine](http://ezinearticles.com/?Prepaid-Versus-Postpaid-Calling---What-To-Use-For-International-Calls\&id=938954), Postpaid \[calling] is a term that is used to refer to a plan in which phone bills are paid on a monthly basis. All of the services that you have used, with their corresponding prices, are added up by the phone company and sent to you in a bill. In contrast, prepaid \[calling] is a term that is used to refer to a scheme that allows you to use the phone company's services based upon the credits remaining on your prepaid card. You will not be able to use any services of the company, if you do not have enough credit. ### TelcoBridges and prepaid & postpaid calling TelcoBridges' Toolpack software and [Tmedia](/products/tmedia/tmedia.md) & Tdev devices support the development of prepaid & postpaid calling applications, such as calling cards. Both families of devices support the deployment of applications that require validation with a database before a call is authorized. For large-scale scenarios, the Tdev platform is recommended. TelcoBridges partners around the world have developed and deployed prepaid & postpaid calling applications. ### References * [Ezine article](http://ezinearticles.com/?Prepaid-Versus-Postpaid-Calling---What-To-Use-For-International-Calls\&id=938954) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://tmediadocs.telcobridges.com/products/tmedia/features-and-solutions/solutions/prepaid-and-postpaid-calling.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.