Astrology app subscriptions: auto-renewal, cancellation and receipts explained

The order should explain the commitment before approval

Before authorising a subscription, look for the product name, included access, currency, amount, billing period and renewal conditions. Any additional profiles, reports or credits should have their own clear treatment. A price displayed in an educational article or a calculator preview is not the same as the final order the customer accepts. The checkout must show the terms that actually apply to that transaction.

Read what starts the access period. It may be tied to a stated activation event rather than simply the moment a price is viewed. Ask how any confirmation deadline is handled and what happens if the service is unavailable. The product should not imply immediate use when an app, store listing or feature is still pending. A waiting-list registration and a paid entitlement are different records and should remain distinguishable.

Antaryami's current public plans state that checkout is not yet open, and its app page marks publication as in preparation. This guide does not change either status. It prepares the reader to examine the actual order when purchasing becomes available. A smooth checkout can still provide full information; fewer clicks should not mean less understanding. The customer should be able to describe the commitment in their own words before approving it, including what renews, what is separate and which official account will hold the resulting records.

Sources: Antaryami: current plans and availability disclosures; Antaryami: public app introduction and release-status labels

Auto-renewal concerns another charge, not just continued visibility

Auto-renewal means the service may create a further charge under the authorised recurring terms. It should not be inferred merely because an account remains accessible or a report stays visible. A one-time pass and a monthly subscription can both have an account screen while differing in future billing. The payment type, period and next-charge information should identify that difference explicitly.

If an introductory price changes after an offer, the customer needs the applicable later amount and the conditions for the change. Do not assume the first displayed price continues indefinitely or that every renewal receives the same promotion. The actual provider-confirmed schedule and order terms matter. A clearly labelled price preview can be useful for planning, but it must not impersonate a quote for changing an existing subscription.

An invented customer might have a paid period ending on a stated date and a later renewal scheduled. Those are two related but distinct facts. If the customer stops renewal, the interface should explain whether the current period continues and when access ends under the service terms. This article deliberately does not supply a real next-charge date or customer mandate. Antaryami's conceptual clock and blank folio introduce the recordkeeping theme without fabricating a transaction. A trustworthy recurring experience makes the billing event visible before it happens, rather than rely on the reader to infer it from the continued presence of a button or a saved profile.

Authorised, captured and access-granted are not interchangeable labels

Razorpay distinguishes payment-authorised and payment-captured events in its payment documentation. A webhook records the entity at the time of that event, so the event name and recorded state need careful handling. This brief provider example is not a claim that a particular Antaryami order has been processed. It illustrates why a customer-facing paid label should be grounded in a verified payment record, not a browser animation alone.

Access is another layer. A service must associate a verified purchase with the correct account and product before displaying the applicable entitlement. Seeing a bank debit, an order-created message or a loading screen does not by itself explain every stage. If the status is unresolved, the customer should be told that clearly and given an official support route. The interface should not encourage repeated payment simply because a confirmation has not yet appeared.

For a hypothetical mismatch, keep the order reference, amount, time and provider transaction reference where available. Do not share passwords, sign-in codes or full card details in a support message. Ask the provider to reconcile the actual record rather than make a second purchase as a troubleshooting step. Antaryami's guide does not promise a resolution timeline or initiate any transaction. It explains a distinction that helps a buyer report a problem precisely: payment state, access state and delivered files are connected operationally, but they are not the same record and should not be collapsed into one vague success message.

Sources: Razorpay: payment webhook events and their recorded status

Cycle-end cancellation and immediate cancellation have different timing

Razorpay's subscription API provides separate immediate and current-cycle-end cancellation options. The exact effect on a customer's app access still depends on the service's entitlement terms and the confirmed operation. A payment-provider capability is not proof that a website has exposed it correctly. The customer should receive an understandable confirmation of what was requested and when it takes effect.

In a hypothetical cycle-end example, the customer asks to stop future renewal while the current paid period runs to its recorded end. That is different from an immediate ending request. A screen should identify the effective date rather than display only a generic cancelled label that leaves the buyer unsure whether current access remains. No real subscription is changed by the example in this article.

Deleting an app, closing a browser or leaving an account unused should not be assumed to submit a cancellation request. Use the actual official route provided for the purchase channel and retain confirmation. If the service was purchased through an app store, inspect that store's current subscription controls and the product's terms rather than assume a website button governs every channel. Antaryami's educational guide does not offer instructions for a verified live cancellation interface. It tells the reader which questions the interface must answer: which subscription, which operation, which effective time and what access remains under the accepted terms. Those details make the process understandable without conflating it with a refund.

Sources: Razorpay: immediate and cycle-end subscription cancellation are different operations

A refund request is a separate question from future renewal

Stopping a future charge does not automatically reverse a previous payment. Conversely, raising a payment dispute or a refund request does not necessarily describe what the customer wants for future access. The service should identify each request separately and explain the applicable terms and rights. An educational article should not replace those terms with a blanket claim that no refund is possible in any circumstance.

For an invented case, a customer may want the current paid period to continue but no later renewal. Another customer may report that the purchased service was never delivered. Those situations deserve different information and records. A support flow should not silently convert one into the other. Keep the reason for the request, the relevant payment and any delivery evidence together so the provider can assess the actual concern.

Do not assume a specific refund entitlement or deadline from this guide. Consult the current published policy, the purchase channel and appropriate professional advice about a disputed case. A refund status also should not be treated as proof of a particular returned amount without the provider-confirmed record. Partial and previous refunds can affect what remains to be reviewed. Antaryami's focus here is clarity rather than adjudication: the customer should know whether they have stopped future billing, ended access, requested money back or received a confirmed repayment. Those events can be related, but their distinct meanings should survive even when a dashboard presents them close together.

A receipt should identify a real payment, not merely resemble paperwork

A useful payment receipt connects a reference, purchase description, amount, currency, recorded status and date. It should not be labelled paid if it represents only a preview or an unresolved order. A logo can make the document recognisable, but branding does not establish the underlying payment state. The record must correspond to the actual transaction the customer is trying to understand.

A payment receipt, a tax invoice and a refund confirmation serve different purposes. Do not assume that a document provides every applicable statutory detail merely because it is downloadable. If a tax document is required for your circumstances, request the appropriate document through the official route and seek qualified advice where necessary. This article does not determine a business's tax status or certify that a particular receipt satisfies a legal requirement.

Keep paperwork accessible through the correct account and avoid exposing it through public links. A transaction reference can help support investigate a concern, but the buyer should still avoid posting private financial information on social platforms. In a household account, a receipt's product and profile association should make clear what was purchased without opening another person's private report indiscriminately. Antaryami's blank receipt artwork contains no fabricated provider reference or customer payment. Its educational role is to introduce the distinction between an attractive document and a verified record, so the reader knows what to inspect before treating either as evidence of a completed purchase.

Owned reports should stay distinct from recurring access

A subscription period concerns access under the accepted plan; a purchased report edition concerns a particular delivered file and its recorded basis. If the product terms preserve an owned edition after access ends, the account should explain how to retrieve it without another purchase. A new or regenerated edition should be clearly identified before any additional charge. Do not assume that every report in a catalogue is included in the subscription.

The history view should help the customer distinguish purchases, renewals and report editions. A useful hypothetical record ties each item to its date, amount and actual deliverable, while retaining the relevant input snapshot for a report. A later profile correction should not silently rewrite what an earlier paid edition represents. Those records give the customer a way to understand their library instead of relying on memory of what a plan once promised.

Sharing a report can reveal another person's birth details and personal interpretations. Use intentional, authenticated access and appropriate permission rather than make the file public because the payment history is visible. The buyer should also know whether a share action sends a file, creates a link or initiates a new generation. Antaryami's separate report-buying guide explains these questions in more detail. This subscription article does not claim its conceptual image demonstrates a released library workflow. It explains why ownership, access period and generation are separate concepts that a neat account screen should make easier to understand, not conceal behind repeated purchase buttons.

Review the account with four questions before the next charge

Ask what is active, what may renew, what has been paid and what files you own. Each question should have a record you can identify. If an answer is unclear, use the official support channel before authorising another purchase. Keep the relevant references privately, and do not assume that a general marketing page can explain the state of your individual account.

For a new buyer, begin with the current Antaryami plans and app-status pages. Read the launch labels and the actual order when checkout opens. For an existing buyer, the provider-confirmed account record and accepted purchase terms matter more than a hypothetical example in an article. This guide makes no changes to a mandate, entitlement or payment. Its purpose is to help you understand those records and ask for clarification where the display does not match them.

A good subscription experience is not only a fast checkout. It includes clear recurring terms, understandable cancellation, accurate paperwork and reliable access to the deliverables the customer bought. Symbolic guidance should remain reflective rather than promise guaranteed outcomes, while commercial records should remain factual rather than symbolic. Antaryami's educational approach keeps those roles separate. The customer can explore the journal at their own pace and make a purchase only when the actual offer is available and understood. Knowing what continues, what stops and what remains owned makes the experience calmer and more useful without requiring the buyer to guess from a label.