ProvelyProve that Square holds an authorisation of the card for this amount. The card issuer authorised the amount, and Square holds the authorisation. This level does not prove a capture. The money did not move.
| Fact | Value |
|---|---|
| Contract id | square.payment.approved |
| Version | 1.0.0 |
| Hash | c09b723501777746 |
| Completion level | approved |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | Square 0.1.0 |
| Valid for provider API versions | 2026-08-19 |
What is the intent?
Get an authorisation of the card for the amount.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | square.payment |
| Canonical effect | payments.card_charge |
| Provider operation | POST /v2/payments |
| Idempotency | idempotency_key, retry is safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- pre existing state
- wrong amount
- wrong subject
The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.
Where do these rules come from?
square.openapi#/paths/~1v2~1payments/post: square.openapi, retrieved 2026-09-08square.openapi#/paths/~1v2~1payments/post/responses/200: square.openapi, retrieved 2026-09-08square.docs.payments#payments/autocomplete-and-the-approved-state/p3: square.docs.payments, retrieved 2026-09-08square.docs.payments#payments/the-status-of-a-payment/p2: square.docs.payments, retrieved 2026-09-08square.openapi#/components/schemas/Payment/properties/id: square.openapi, retrieved 2026-09-08square.openapi#/paths/~1v2~1payments~1{payment_id}/get/responses/200: square.openapi, retrieved 2026-09-08square.openapi#/components/schemas/Payment/properties/status: square.openapi, retrieved 2026-09-08square.docs.payments#payments/the-status-of-a-payment/p3: square.docs.payments, retrieved 2026-09-08square.openapi#/components/schemas/Payment/properties/amount_money: square.openapi, retrieved 2026-09-08square.openapi#/components/schemas/Money/properties/amount: square.openapi, retrieved 2026-09-08square.docs.payments#payments/amounts/p1: square.docs.payments, retrieved 2026-09-08square.openapi#/components/schemas/Money/properties/currency: square.openapi, retrieved 2026-09-08square.docs.payments#payments/amounts/p2: square.docs.payments, retrieved 2026-09-08square.openapi#/components/schemas/Payment/properties/created_at: square.openapi, retrieved 2026-09-08square.docs.payments#payments/identifiers/p2: square.docs.payments, retrieved 2026-09-08square.events#/events/payment.created: square.events, retrieved 2026-09-08square.docs.webhooks#webhooks/the-event-types/p2: square.docs.webhooks, retrieved 2026-09-08square.docs.webhooks#webhooks/the-event-types/p7: square.docs.webhooks, retrieved 2026-09-08
Can square.payment.approved return VERIFIED from the action response alone?
No. The action response is E1, and an acknowledgement is never terminal success. The contract needs evidence of level E2 or higher from Square.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.