You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
How does Payment Kit connect apps, identity and payments?
A cross-topic application component evolving from the legacy Blocklet version to ARC 3.
Payment Kit provided billing, subscriptions and checkout as a Blocklet. Its 2024 launch described crypto payments and Stripe-based fiat integration, so it is broader than crypto payment.
Version continuity: PaymentKit continues as a product, with a smooth upgrade from its legacy Blocklet version to ARC 3 underway. Maintenance ends for the old version, not the product. DiscussKit’s relaunch illustrates the same continuity. Historical documentation is not a new-version installation guide or a guarantee of feature parity.
Connections on the map
| Connection | Question |
|---|---|
| Blocklet | How is payment functionality composed into an app? |
| Payments / crypto payments | How are orders separated from settlement channels? |
| DID / Arc Wallet | Which party participates and controls credentials? |
| AI agent | Who authorizes programmatic spending and limits it? |
| ARC | What runs the next application version? |
A payment record aids reconciliation; it proves neither purchasing authority nor service delivery. Verify agent delegation and evidence capabilities individually.
Sources and further reading
Check your understanding
Was Payment Kit limited to crypto payments?
No. Historical releases also integrated fiat payments through Stripe; channels depend on configuration.
Continue along a learning path
- From runtime foundations to applicationsStep 9 of 10