ProvelyProve that the money of this capture moved from the payer to the payee. The captured payment reached the status COMPLETED. A 201 Created answer with the status PENDING is an object that exists and not money that moved.
| Fact | Value |
|---|---|
| Contract id | paypal.capture.completed |
| Version | 1.0.0 |
| Hash | a90c595b2f9203ed |
| Completion level | capture_completed |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | PayPal REST API 0.1.0 |
| Valid for provider API versions | v2 |
What is the intent?
Capture the payment of the approved order and let the money move.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | paypal.capture |
| Canonical effect | money.capture |
| Provider operation | POST /v2/checkout/orders/{id}/capture |
| Idempotency | idempotency_key through PayPal-Request-Id, 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?
paypal.payments.openapi#/components/schemas/capture_status/properties/status: paypal.payments.openapi, retrieved 2026-09-08paypal.docs.captures#captured-payments/the-status-of-a-captured-payment: paypal.docs.captures, retrieved 2026-09-08paypal.events#/events/PAYMENT.CAPTURE.COMPLETED: paypal.events, retrieved 2026-09-08paypal.docs.captures#captured-payments/capture-a-payment: paypal.docs.captures, retrieved 2026-09-08paypal.payments.openapi#/components/schemas/capture: paypal.payments.openapi, retrieved 2026-09-08paypal.payments.openapi#/paths/~1v2~1payments~1captures~1{capture_id}/get/responses/200: paypal.payments.openapi, retrieved 2026-09-08paypal.orders.openapi#/components/schemas/payment_collection/properties/captures: paypal.orders.openapi, retrieved 2026-09-08paypal.payments.openapi#/components/schemas/related_ids/properties/order_id: paypal.payments.openapi, retrieved 2026-09-08paypal.payments.openapi#/components/schemas/capture-2: paypal.payments.openapi, retrieved 2026-09-08paypal.payments.openapi#/components/schemas/money/properties/value: paypal.payments.openapi, retrieved 2026-09-08paypal.payments.openapi#/components/schemas/money/properties/currency_code: paypal.payments.openapi, retrieved 2026-09-08paypal.payments.openapi#/components/schemas/activity_timestamps/properties/create_time: paypal.payments.openapi, retrieved 2026-09-08paypal.docs.captures#captured-payments/events: paypal.docs.captures, retrieved 2026-09-08
Can paypal.capture.completed 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 PayPal REST API.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.