Release identity
SHA-256 of the pack file bytes: 545c3f83b9b584419879c3297b6de82f8d2d0c1da59885baa8d07e787a984c83
Distributable: digest matches the release manifest. The binary carries a digest-bound manifest of the distributable library; a pack whose bytes differ from its manifest entry — endpoint, tier, allowlist, or credential edited, with provider, version, and review block preserved — fails the digest check, loses distributability, and renders MODIFIED rather than as the shipped reviewed artifact. Review state and artifact status are different facts: the first is a documentation-review declaration, the second is the identity of the exact bytes.
Capabilities (5)
stripe.payment_intents.read v1.0.0R0
- Action
- read
- Endpoint
GET https://api.stripe.com/v1/payment_intents- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-stripe-restricted-key- Data class
- financial
Read payment intents.
stripe.customers.read v1.0.0R0
- Action
- read
- Endpoint
GET https://api.stripe.com/v1/customers- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-stripe-restricted-key- Data class
- pii
Read customer records, which carry personal data.
stripe.payment_intents.create v1.0.0R3
- Action
- pay
- Endpoint
POST https://api.stripe.com/v1/payment_intents- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-stripe-restricted-key- Data class
- financial
Create a PaymentIntent. Creation can request confirmation, so one call can result in a completed payment; the action is pay at the R3 floor — a conservative floor, since creation alone may only authorize — and pay is one of the IRREVERSIBLE ACTIONS (delete, send, pay, deploy, approve, share and transfer). The registered cost ceiling is a budget control on the declared amount: the gateway refuses a declared amount above it and commits the ceiling against the work budget; it does not bound the amount the provider request encodes — currency and minor units are the deployment's review.
stripe.refunds.create v1.0.0R3
- Action
- pay
- Endpoint
POST https://api.stripe.com/v1/refunds- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-stripe-restricted-key- Data class
- financial
Refund a payment: money moves back, so the action is pay at the R3 floor; pay is one of the IRREVERSIBLE ACTIONS (delete, send, pay, deploy, approve, share and transfer). A refund request may omit the amount and return the remaining refundable total, so the registered cost ceiling — a budget control on the declared amount — does not bound what the provider moves.
stripe.customer.delete v1.0.0R3
- Action
- delete
- Endpoint
DELETE https://api.stripe.com/v1/customers/CUSTOMER_ID- Connector
- http
- Custody
- customer_vault
- Credential ref
secret-ref-stripe-restricted-key- Data class
- pii
Delete a customer record. CUSTOMER_ID is a placeholder to replace before enabling.
Credential reference
The pack names a reference, never a secret. Installing a pack registers capabilities and makes them governable; registration is not connectivity. The credential is created at the provider and held in the client's own secret manager under the reference the pack names, and deployment testing is still required to show the credential path works and cannot be bypassed.
- Reference
secret-ref-stripe-restricted-key- Custody
- customer_vault
- Injection
- header (Authorization)
A Stripe restricted API key held in the client's own secret manager. The stored material must be the complete Authorization header value (scheme included). Live and test keys are different credentials: point this reference at the live key only when the deployment is meant to move real money.
Resources
stripe-account(api, financial):https://api.stripe.com/v1
Pack notes and exclusions
Use a restricted API key with only the permissions these capabilities need; the pack does not create one. A PaymentIntent does not invariably move money at creation — creation can request confirmation, and whether money moves then depends on the confirmation, the capture method and the payment method — but a single call can result in a completed payment, so the capability stays conservatively at the pay action's R3 floor, and pay is one of the IRREVERSIBLE ACTIONS (delete, send, pay, deploy, approve, share and transfer); a policy budget is the second control. Stripe names the Charges API a legacy API and directs new integrations to PaymentIntents, with new features landing in the PaymentIntents API only, so this pack's money movement runs on PaymentIntents; the pack is version 1.1.0 because the money path moved on 2026-09-20, and a deployment that registered the 1.0.0 Charges capabilities keeps those registered versions until they are retired under change control — installing this pack does not retire them.
Review record
Review completed: 2026-09-20 · Reviewer: aaes-eng (an opaque id that resolves internally to the responsible reviewer)
- https://docs.stripe.com/api/payment_intents (retrieved 2026-09-20)
- https://stripe.com/docs/charges (retrieved 2026-09-20)
- https://docs.stripe.com/payments/payment-intents/migration/charges (retrieved 2026-09-20)
A pack review is not a vendor or examiner attestation. A retrieval date says when a source page was read; it does not by itself establish what the page said then. No pack is vendor-endorsed, and none has been connectivity-tested against a live vendor tenant.