ProvelyNo. Stripe returns a success response when it accepts the request. Provely proves created and succeeded as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Official |
| Last conformance run | 2026-09-05T12:00:00Z: 33 of 33 cases passed, 0 critical false VERIFIED |
| Provider API versions | 2026-08-26 |
| Default provider API version | 2026-08-26 |
| Compiled | 2026-09-05 |
| Manifest hash | 13108798680f04f5 |
| Manifest hash check | the document hashes to the value the manifest states |
| Signature | valid, key provely-skill-2026-09, trusted by this build |
What does this page prove?
| Claim | Proven by | Evidence | Status |
|---|---|---|---|
| The created level proves that the Refund object exists at the provider with the requested amount and charge. It does not prove that money moved. | stripe.refund.created | E2 + E3 | proven |
| A Refund object does not prove that money moved. This contract proves the succeeded state on the refund resource and a refund.updated event that carries it. | stripe.refund.succeeded | E2 + E3 | proven |
| An outcome outside Stripe, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the Stripe skill expose?
Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.
| Level | Contract | Promise | Evidence | Certification |
|---|---|---|---|---|
created | stripe.refund.created v1.0.0 | The created level proves that the Refund object exists at the provider with the requested amount and charge. It does not prove that money moved. | E2 + E3 | Official |
succeeded | stripe.refund.succeeded v1.0.0 | A Refund object does not prove that money moved. This contract proves the succeeded state on the refund resource and a refund.updated event that carries it. | E2 + E3 | Official |
Which ways can a Stripe action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| stripe.refund.created | duplicate side effect | CONTRADICTED |
| stripe.refund.created | pre existing state | CONTRADICTED |
| stripe.refund.created | wrong amount | CONTRADICTED |
| stripe.refund.created | wrong subject | CONTRADICTED |
| stripe.refund.succeeded | duplicate side effect | CONTRADICTED |
| stripe.refund.succeeded | pre existing state | CONTRADICTED |
| stripe.refund.succeeded | wrong amount | CONTRADICTED |
| stripe.refund.succeeded | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 33 of 33 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
stripe.refund.created | Official |
stripe.refund.succeeded | Official |
The weakest contract is stripe.refund.created. It reaches Official. The package level is Official, because a package level never rises above its weakest contract. Read the level of the contract you use.
| Case class | Passed | Total |
|---|---|---|
| duplicate side effect | 2 | 2 |
| error after execution | 2 | 2 |
| error before execution | 2 | 2 |
| evidence unavailable | 2 | 2 |
| idempotent retry | 2 | 2 |
| pre existing state | 3 | 3 |
| stale readback | 2 | 2 |
| still transitional | 2 | 2 |
| terminal failure | 2 | 2 |
| terminal success | 2 | 2 |
| timeout after commit | 2 | 2 |
| version mismatch | 2 | 2 |
| webhook duplicate | 2 | 2 |
| webhook out of order | 2 | 2 |
| wrong amount | 2 | 2 |
| wrong subject | 2 | 2 |
The conformance artifact digest is 1246b0a1a0b70982. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
Every rule this skill states comes from a source. No question is open.
What happens to a Stripe verdict when Stripe is down?
Nothing changes about the verdict. Provely records whether Stripe answered when it read it, and it reads what Stripe publishes about itself. Both explain an answer. Neither decides one. Read how Provely records integration uptime.
Stripe publishes a machine-readable status document at https://status.stripe.com/current. Provely reads it on a schedule and stores what it says. A JSON document with a per-component status map, an overall largestatus, and a message.
Source: Stripe status page · retrieved 2026-09-07
A Stripe status page is second-hand. It is often late, and it is often narrower than the outage. A verdict never rests on it.
Where do these facts come from?
Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.
| Source | Kind | Retrieved | Excerpt |
|---|---|---|---|
| stripe.docs.idempotency | docs | 2026-09-05 | authored |
| stripe.docs.refunds | docs | 2026-09-05 | authored |
| stripe.docs.webhooks | docs | 2026-09-05 | authored |
| stripe.events | event sample | 2026-09-05 | authored |
| stripe.openapi | openapi | 2026-09-05 | trimmed |
How do I verify a Stripe action?
Verify a Stripe action with Provely
- Begin the operation.Call
beginwith the contractstripe.refund.createdand the input. Keep the operation id and the idempotency key. - Make the Stripe call you make today.Send the
Idempotency-Keyheader with the key thatbeginreturned. A retry then cannot create a second side effect. - Submit the acknowledgement.Call
action_resultwith the Stripe response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from Stripe and not from the agent, and evaluates the contract. - Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.
Questions developers ask
Does the created level prove the succeeded level?
No. The created level proves that the Refund object exists at the provider with the requested amount and charge. It does not prove that money moved. A Refund object does not prove that money moved. This contract proves the succeeded state on the refund resource and a refund.updated event that carries it. Use stripe.refund.succeeded to prove succeeded.
What does the agent say while the Stripe action is still in progress?
It says: "The action is accepted but not yet verified. Operation: <id>." The verdict is PENDING. The runtime observes again on the contract timing policy.
Which Stripe API versions does the skill support?
2026-08-26. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to Stripe?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where Stripe permits it, and it never shares that credential with the agent.