This page describes AAES Govern’s controls. AAES Operate has private-work permissions, operational reviews and recorded-spend limits; it does not include Govern. About AAES Govern
Before you enable this package
Budgets apply to the amount declared in the task, not to the amount the provider actually sends or moves. A refund request may omit the amount, in which case Stripe refunds the full remaining refundable total. CUSTOMER_ID is a placeholder to replace before enabling.
Read each action's effects and exclusions below. Before installation, also read the complete package requirements, including credential issuance, scope, expiry, and provider permissions. These are deployment prerequisites, not capabilities this package supplies.
Capabilities (5)
Each capability below is one registered operation. The complete package JSON includes its exact network destination allowlist. The repository stores it at packs/stripe.json and embeds a copy in the release binary.
Versions. This package is version 1.1.0. Its capabilities carry their own version numbers: 2 at version 1.1.0, 3 at version 1.0.0, as shown on each capability below.
Risk tiers. R0 is the minimum for reads. R2 is the minimum for write, create, update, execute, and invoke. R3 is the minimum for delete, send, pay, deploy, approve, share, and transfer. Operators can raise these levels. A minimum tier does not measure the operation's business or confidentiality risk.
On supported execution paths routed through AAES Govern, the R3 actions listed below require approval by an authorized person. Bypass paths and observation-only registrations are outside that guarantee. A provider's restoration feature does not remove this approval requirement. A provider-side approval, such as approving a GitLab merge request, is also separate from AAES Govern human approval. The capability matrix shows which execution paths are implemented, restricted to lab use, or refused at startup. Live compatibility must be tested in your environment.
Field guide. Endpoint is the service address and request method. Connector is the adapter that makes the call. Custody describes how the credential is held; the credential reference identifies the value to resolve. Data class sets handling requirements: pii means personal data, financial means financial records, and internal means internal organizational data.
stripe.payment_intents.read v1.1.0R0
- Kind
- tool
- 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.
Read payment intents.
stripe.customers.read v1.0.0R0
- Kind
- tool
- 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 customers.
Read customer records, which carry personal data.
stripe.payment_intents.create v1.1.0R3
- Kind
- tool
- 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 payment intents.
Create a PaymentIntent. Creation can request confirmation, so one call can result in a completed payment; the action is pay at the minimum R3 tier — a conservative minimum, since creation alone may only authorize — and pay is one of the designated actions requiring human approval.
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
- Kind
- tool
- 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
Create refunds.
Refund a payment: money moves back, so the action is pay at the minimum R3 tier; pay is one of the designated actions requiring human approval. 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
- Kind
- tool
- 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 customer.
Delete a customer record. CUSTOMER_ID is a placeholder to replace before enabling.
Credential reference
The credential field names a reference rather than containing credential material. Packs are designed not to contain secrets; the format checks cover only known credential formats and cannot prove that arbitrary text contains no secrets. Installing a package registers its capabilities. Configure the provider credentials, endpoints, and network access, then test the integration in your environment before enabling it.
- Reference
secret-ref-stripe-restricted-key- Custody
- customer_vault
- Injection
- header (Authorization)
Configure the value and injection format specified in the package. Assign responsibility for credential rotation and revocation, restrict provider permissions, and keep credential material out of logs and responses.
Complete credential requirements
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
Technical package and review record
Complete provider requirements 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 designated actions requiring human approval; 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. The two PaymentIntents capabilities were introduced in pack version 1.1.0 and carry that version; the customer and refund capabilities are unchanged since 1.0.0 and keep it, because a capability's version is the pack version in which its registration last changed.
Download the complete package JSON for exact network allowlists, credential requirements, exclusions, and setup notes. Read these requirements before installation.
The full documentation review record is supplied in the evaluation package. The evaluation package runs in your environment and comes only with the paid design partnership. This page reproduces the source links and review block; the full record is available for evaluation. Discuss a design partnership to inspect it before installation.
Review block
This section reproduces the review block recorded in the pack file. The evidence and approval record is separate: for a reviewed pack, it is in the evaluation materials and in the release binary's embedded assets.
Review completed: 2026-10-22
7 sources, retrieved 2026-09-20, 2026-09-23
- 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)
- https://docs.stripe.com/api/refunds/create (retrieved 2026-09-23)
- https://docs.stripe.com/api/customers/delete (retrieved 2026-09-23)
- https://docs.stripe.com/api/authentication (retrieved 2026-09-23)
- https://docs.stripe.com/api/customers/list (retrieved 2026-09-23)
Current documentation links are navigation aids. They do not change the package, its historical sources or its review date. Review dates describe a documentation review, not a live integration test. No package is provider-endorsed or yet tested against a live provider tenant.
Release identity
SHA-256 of the pack file bytes: 5b23b6de4b4f5224a969cda72dd31b061d84dc89c59a282bf947d33445ff2acb
Distributable: yes, digest matches the release manifest. Editing a package changes its release identity. A deployment plan checks its own file digests; it does not restore reviewed status or authenticate approval.