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

P2Flux API Recurring payments API

Signed once by the customer, charged by your renewal job.

P2Flux API Recurring payments API is one of 6 APIs that P2Flux API 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, an API reference, and authentication docs.

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

Requests are made against 2 base URLs: https://api.p2flux.com, https://api-test.p2flux.com.

8 operations 8 paths 9 schemas 8 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.p2flux.com
Contact
Resource Areas
1

Paths & Operations 8

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

Recurring Payments 8

Signed once by the customer, charged by your renewal job.

POST
/v1/allowances/restore/resolve
Read an allowance-restore session back
resolveAllowanceRestore body → 200400429
POST
/v1/allowances/restore/session
Session for restoring the allowance one subscription needs
createAllowanceRestoreSession body → 200400429
POST
/v1/charges
Execute one recurring charge
charge body → 200400409429502503
POST
/v1/charges/recover
Find the transaction that charged one recurring period
recoverCharge body → 200400409429502503
POST
/v1/subscriptions
Create subscription terms and a setup token
createSubscription body → 200400
POST
/v1/subscriptions/finalize
Exchange a signature for a charge capability
finalizeSubscription body → 200400429502503
POST
/v1/subscriptions/resolve
Authoritative terms plus the EIP-712 payload to sign
resolveSubscription body → 200400
POST
/v1/subscriptions/status
Current state, read from the chain
subscriptionStatus body → 200400429502503

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed is Error (2 properties). Each schema is shown below with its type and property counts.

Bytes32
string
A 32-byte hex value, lowercase. Transaction hashes and references.
ErrorCode
string
Every code this API can return. Stable identifiers - branch on these, never on the human-readable text or the HTTP status alone.
Address
string
An EVM address.
Signature
string
An EIP-712 signature. Contract wallets (ERC-1271) are supported.
AmountUnits
string
An integer count of micro-USDC (6 decimals), as a string. 2500000 is 2.50 USDC. Used wherever a decimal would invite a rounding error - notably refund amounts.
Error
object
The uniform error envelope. error is the P2Flux code; action is what a merchant system should do about it, so integrations never hard-code that table themselve…
2 properties 1 required
MerchantAction
string
What to do about a result. - SUCCESS - done, nothing owed. - WAIT - the money may already have moved. The transaction exists and has not settled to the require…
Token
string
A signed P2Flux capability: payment intent (p2f1.), setup token (p2setup2.), subscription capability (p2s2.), cancel token (p2cancel1.) or refund token (p2refu…
Amount
string
A USDC amount as a decimal string, up to 6 decimal places. Never a JSON number: binary floating point cannot represent most decimal prices exactly, and this is…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

p2flux-api-recurring-payments-api-openapi.yml Raw ↑

Other APIs P2Flux API publishes across the network.

P2Flux API Cancellation API
P2Flux API One-time payments API
P2Flux API Refunds API
P2Flux API Service API
P2Flux API Subscriptions API
Where this information came from

This is an independent, third-party profile of P2Flux API 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.