> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/recurring-payments-coming-soon.md).

# Recurring Payments (coming soon)

Recurring Payments lets you take a payment method once on Coda’s Hosted Payment Page, keep that instrument on file with the customer’s consent, and charge it again from your own backend whenever *you* decide to bill — renewals, top-ups, or unscheduled charges — without Coda running a subscription calendar for you.

You keep control of schedule, retries, and entitlement. Coda handles the customer-present save, scheme-compliant reuse, and a secure Token Charge API so later payments complete with the shopper absent, using the same Init, notification, and Inquiry path you already know.

{% hint style="danger" %}
This product is currently available for card payments only. Support for alternative payment methods will be expanded in the future
{% endhint %}

#### Integration Assumptions

This documentation assumes that scheduling and subscription lifecycle management are handled on the client side. This includes:

* Plan creation and pricing
* Billing intervals and scheduling
* Cancellations and status management

{% hint style="info" %}
Coda does **not** schedule recurrences, manage subscriptions, or decide when to bill. Your backend decides **when** to charge. Coda provides:

1. A customer-present **Init / Hosted Payment Page** flow that can save a card for later reuse (**CIT-for-MIT**).
2. A server-to-server **Token Charge** API for later charges with the customer absent (**MIT**).
   {% endhint %}

#### Key Capabilities

The Recurring Payments product provides the following core capabilities:

* Account Binding With First Charge: Allows you to save a payment method while simultaneously completing an initial charge.
* User-Initiated & Merchant-Initiated Payments: Supports both real-time payments authorized by users (on-session) and payments initiated by the merchant for subscriptions (off-session).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coda.co/codapay/recurring-payments-coming-soon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.