JiesdaPay 文档Payment rails
How JiesdaPay works with payment providers and machine-readable payment protocols.
JiesdaPay is rail-agnostic.
It is designed to work around existing payment providers, wallet flows, and machine-readable protocols such as x402. The product value is the control layer around the paid call, not ownership of the money movement itself.
What a rail does
A payment rail can:
- Charge a card or account.
- Confirm a payment token.
- Represent a wallet payment.
- Support an x402-style machine payment flow.
- Return a payment event.
The rail answers how payment happens.
What JiesdaPay does
JiesdaPay answers:
- Who is allowed to spend?
- Why is the call being made?
- Which scope applies?
- How much may this task spend?
- Does this call need approval?
- How should the event be audited?
This means JiesdaPay can work with many rails without becoming a replacement for them.
First-phase money flow
In the first phase, JiesdaPay should not custody user funds.
Developers can bind their own collection method or payment rail. JiesdaPay records the payment and agent-call events and connects them into an audit ledger.
This keeps the MVP focused and avoids pretending to be a payment institution.