ProvelyNo. Square returns a success response when it accepts the request. Provely proves approved, completed and refunded as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Last conformance run | 2026-09-05T12:00:00Z: 52 of 52 cases passed, 0 critical false VERIFIED |
| Provider API versions | 2026-08-19 |
| Default provider API version | 2026-08-19 |
| Compiled | 2026-09-05 |
| Manifest hash | 5b92b4a15b5a20ca |
| 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 card issuer authorised the amount, and Square holds the authorisation. This level does not prove a capture. The money did not move. | square.payment.approved | E2 + E3 | proven |
| An approved payment is an authorisation hold, not a captured payment. This level reads the payment status and the card timeline together. | square.payment.completed | E2 + E3 | proven |
| A PaymentRefund object does not prove that money moved. This level proves the COMPLETED state on the refund and an event that carries it. | square.refund.completed | E2 + E3 | proven |
| An outcome outside Square, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The meaning of a Square state that no source states | not proven | no source states it | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the Square 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 |
|---|---|---|---|---|
approved | square.payment.approved v1.0.0 | The card issuer authorised the amount, and Square holds the authorisation. This level does not prove a capture. The money did not move. | E2 + E3 | Provisional |
completed | square.payment.completed v1.0.0 | An approved payment is an authorisation hold, not a captured payment. This level reads the payment status and the card timeline together. | E2 + E3 | Provisional |
refunded | square.refund.completed v1.0.0 | A PaymentRefund object does not prove that money moved. This level proves the COMPLETED state on the refund and an event that carries it. | E2 + E3 | Provisional |
Which ways can a Square action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| square.payment.approved | duplicate side effect | CONTRADICTED |
| square.payment.approved | pre existing state | CONTRADICTED |
| square.payment.approved | wrong amount | CONTRADICTED |
| square.payment.approved | wrong subject | CONTRADICTED |
| square.payment.completed | duplicate side effect | CONTRADICTED |
| square.payment.completed | pre existing state | CONTRADICTED |
| square.payment.completed | wrong amount | CONTRADICTED |
| square.payment.completed | wrong subject | CONTRADICTED |
| square.refund.completed | duplicate side effect | CONTRADICTED |
| square.refund.completed | pre existing state | CONTRADICTED |
| square.refund.completed | wrong amount | CONTRADICTED |
| square.refund.completed | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 52 of 52 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
square.payment.approved | Provisional |
square.payment.completed | Provisional |
square.refund.completed | Provisional |
The weakest contract is square.payment.approved. It reaches Provisional. The package level is Provisional, 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 | 3 | 3 |
| error after execution | 3 | 3 |
| error before execution | 3 | 3 |
| evidence unavailable | 3 | 3 |
| idempotent retry | 3 | 3 |
| pre existing state | 3 | 3 |
| stale readback | 3 | 3 |
| still transitional | 3 | 3 |
| terminal failure | 3 | 3 |
| terminal success | 3 | 3 |
| timeout after commit | 3 | 3 |
| version mismatch | 3 | 3 |
| webhook duplicate | 3 | 3 |
| webhook out of order | 3 | 3 |
| wrong amount | 3 | 3 |
| wrong resource | 1 | 1 |
| wrong subject | 3 | 3 |
| wrong terminal state | 3 | 3 |
The conformance artifact digest is d375359d3d20fb3f. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
The level is Provisional because of it. Provely does not guess a rule that a source does not state.
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 |
|---|---|---|---|
| square.docs.idempotency | docs | 2026-09-08 | authored |
| square.docs.payments | docs | 2026-09-08 | authored |
| square.docs.refunds | docs | 2026-09-08 | authored |
| square.docs.versions | docs | 2026-09-08 | authored |
| square.docs.webhooks | docs | 2026-09-08 | authored |
| square.events | event sample | 2026-09-08 | authored |
| square.openapi | openapi | 2026-09-08 | trimmed |
How do I verify a Square action?
Verify a Square action with Provely
- Begin the operation.Call
beginwith the contractsquare.payment.approvedand the input. Keep the operation id. - Make the Square call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the Square response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from Square 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 approved level prove the refunded level?
No. The card issuer authorised the amount, and Square holds the authorisation. This level does not prove a capture. The money did not move. A PaymentRefund object does not prove that money moved. This level proves the COMPLETED state on the refund and an event that carries it. Use square.refund.completed to prove refunded.
What does the agent say while the Square 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 Square API versions does the skill support?
2026-08-19. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to Square?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where Square permits it, and it never shares that credential with the agent.