ProvelyProve that PayPal holds a captured payment for this order. The captured payment exists with the intended order, amount, and currency. A 201 Created answer with the status PENDING proves that no money moved.
| Fact | Value |
|---|---|
| Contract id | paypal.capture.recorded |
| Version | 1.0.0 |
| Hash | 2331d39709d51d40 |
| Completion level | capture_recorded |
| 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.
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?
- 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.orders.openapi#/paths/~1v2~1checkout~1orders~1{id}~1capture/post: paypal.orders.openapi, retrieved 2026-09-08paypal.orders.openapi#/paths/~1v2~1checkout~1orders~1{id}~1capture/post/responses/201: paypal.orders.openapi, retrieved 2026-09-08paypal.docs.captures#captured-payments/capture-a-payment: paypal.docs.captures, retrieved 2026-09-08paypal.docs.captures#captured-payments/a-pending-capture: 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.events#/events/PAYMENT.CAPTURE.COMPLETED: paypal.events, retrieved 2026-09-08paypal.events#/events/PAYMENT.CAPTURE.PENDING: paypal.events, retrieved 2026-09-08paypal.docs.captures#captured-payments/events: paypal.docs.captures, retrieved 2026-09-08
Can paypal.capture.recorded 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.