How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Cash App

Cash App Recurring Payments API

The Recurring Payments API from Cash App — 2 operation(s) for recurring payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cash App Recurring Payments API is one of 25 APIs that Cash App publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Recurring Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://global-api-sandbox.afterpay.com, https://global-api.afterpay.com.

2 operations 2 paths 26 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.cash.app/network/v1
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

Cash App Recurring Payments API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (sec0).

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Recurring Payments 2
POST
/v2/recurring-payments
Capture Full Recurring Payment
capture-full-recurring-payment 3 params body → 201402415422
POST
/v2/recurring-payments/auth
Authorize Recurring Payment
auth 3 params body → 201402412415422

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are RecurringPaymentRequest (17 properties), Payment (11 properties), PaymentAuth (11 properties), Item (9 properties). Each schema is shown below with its type and property counts.

PaymentAuthStatus
string
represents the status of the order
RecurringPaymentRequestPaymentMethod
object
2 properties 2 required
PaymentEventType
string
Payment
object
Describes the schema for a (read-only) payment object
11 properties
ShippingCourierPriority
string
Payment-Event
object
Each payment event has a unique ID, creation timestamp, and type (e.g., "AUTHAPPROVED", "AUTHDECLINED"). For "AUTHAPPROVED" events, an expiration timestamp is…
6 properties
Shipping-Courier
object
Essential information for tracking a shipment. The shippedAt key represents the date and time when the item was shipped. This value follows the [ISO 8601 stand…
4 properties
PaymentAuthPaymentState
string
is the current state for capturing payments
Contact
object
This data model is used for storing an individual's contact information. Mandatory fields such as name, line1, area1, region, postcode, and countryCode help in…
9 properties 6 required
Consumer
object
The consumer data model is used for gathering essential user information. It captures details such as the individual's first name, represented by givenNames, a…
4 properties 1 required
PaymentStatus
string
represents the status of the order
Item
object
This data model is used to store crucial product details. The price.amount field represents the unit price of the individual item. The quantity field shows the…
9 properties 3 required
RecurringPaymentRequestMerchant
object
1 property
RecurringPaymentRequestEnrichments
object
1 property
RecurringPaymentRequestEnrichmentsInitiationActor
string
The actor initiating the transaction. Use MERCHANT when the customer is not present.
Money
object
Object containing amount and currency
2 properties 2 required
RecurringPaymentRequestEnrichmentsInitiation
object
Describes who initiated the transaction
1 property
MoneyCurrency
string
ContactCountryCode
string
Discount
object
Discount applied to an order
2 properties
PaymentPaymentState
string
is the current state for capturing payments
Order-Details
object
This comprehensive schema is designed to store an entire transaction's detail, covering crucial aspects like consumer information, billing and shipping details…
7 properties
PaymentAuth
object
Describes the schema for a (read-only) payment object
11 properties
Refund
object
To guarantee safe retries, the merchant should offer their refund ID or reference, aligning with their internal records Unique values for the requestID and mer…
6 properties
RecurringPaymentRequest
object
17 properties 3 required
RecurringPaymentRequestPaymentMethodType
string
The payment method type

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cash-app-recurring-payments-api-openapi.yml Raw ↑

Other APIs Cash App publishes across the network.

Cash App Add Cash App Pay To Your Site API
AE Profile APIs.io
Cash App Balances API
AE Profile APIs.io
Cash App Billing Agreements (Deprecated) API
AE Profile APIs.io
Cash App Brands API
AE Profile APIs.io
Cash App Customer Request API
AE Profile APIs.io
Cash App Customers API
AE Profile APIs.io
Cash App Disputes API
AE Profile APIs.io
Cash App Grants Afterpay API
AE Profile APIs.io
Cash App Merchants API
AE Profile APIs.io
Cash App Network API
AE Profile APIs.io
Cash App Payments API
AE Profile APIs.io
Cash App Payouts API
AE Profile APIs.io
#Recurring Payments
← Back to C APIs
API Details
ID
cash-app:cash-app-recurring-payments-api
Base URL
https://api.cash.app/network/v1
Docs
https://developers.cash.app/cash-app-pay-partner-api/api-reference/network-api
Provider
Cash App
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cash-app-recurring-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cash-app-recurring-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cash App Recurring Payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.