158910 :: docs: AutoPay developer section

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.

[ankitottu]

Redmine #158910 · epic #158909

Adds the AutoPay developer documentation at /developers/payments/autopay/, following the M-Wallet section and the order mandated by docs/developers/CLAUDE.md.

What changed

File
docs/developers/payments/autopay/index.mdx	the page
src/diagrams/AutoPayFlowDiagram.tsx	inline theme-aware SVG, matching WalletFlowDiagram / RecurringFlow. Not Mermaid
docs/developers/payments/index.md	AutoPay card + "Choose Your Path" row
src/data/glossary-terms.ts	subscription, billing cycle, dunning
docs/developers/cards-and-tokens/recurring-payments.mdx	reverse half of the deconfliction cross-link

sidebars.ts is untouched — both AutoPay sidebar blocks landed in the scaffold commit on the epic branch so this lane and the business lane share zero files.

The deconfliction (R5) is the highest-value edit

recurring-payments.mdx already documents payment_type=auto_debit and is the closest analog, so readers land on the wrong page. Both pages now cross-link with an explicit "use this when":

with auto_debit the merchant owns the schedule, retries and dunning; with auto_payAutoPay owns them.

Three facts documented that appear in no ticket

Found while verifying against autopay/subscriptions/api.py and a live betabulk call:

1. The autopay request block is write-only — not echoed in the 201. extra.autopay.subscription_id is the merchant's only handle.
2. customer_email is required. Omitting it makes AutoPay's internal schema 422 at bind time, which Connect surfaces as 400 {"autopay":["AutoPayClient rejected request (422)"]} — reads like an agreement-shape error and is not.
3. page-link does not rotate the token; regenerate-page-token revokes. A merchant reaching for regenerate when they meant re-send silently breaks the customer's working link, with no notification to that customer.

Blocked, deliberately

## API Reference is a placeholder. core_backend PR 121 has not merged, so the public OpenAPI schema serves zero AutoPay endpoints (static/Ottu_API.yaml has no autopay occurrence) and <ApiDocEmbed> cannot resolve. The six endpoints are documented as prose and cURL under ## Guide instead. No embed was fabricated.

⚠️ Needs backend confirmation before merge

The endpoint samples use AutoPay's own root-mounted paths (/subscriptions/...). Those are correct for the service itself, but merchants reach it through a Connect proxy whose public path lives in PR 121 and is not confirmed. @yamen — what is the merchant-facing base path?

Test plan

• npm run typecheck passes
• npm run build passes on the epic base; no new broken-anchor warning naming an AutoPay path
• sidebar anchors #when-to-use, #guide, #api-reference, #best-practices, #faq all resolve to real headings
• no hardcoded Ottu base URL in any code block — OTTU_CONNECT_BASE_URL + <CodeBlock> throughout

Do not merge — review first.