> 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)

The Recurring Payments product enables you to securely store and reuse a shopper’s payment method for future transactions. This infrastructure supports seamless subscription billing, one-click payments, and various recurring scenarios by reducing friction in the payment experience.

Built on our existing payment stack, this solution leverages wide coverage while extending capabilities to include payment method binding, tokenized payments, and off-session transactions.

{% 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

#### 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 automated payments initiated by the merchant for subscriptions (off-session).
* Fetching Saved Payment Methods: Enables you to retrieve and manage a shopper’s stored payment methods to facilitate future transactions.


---

# 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.