Signal Supply Co.
user_action vs commit
Run a real Orders V2 + JS SDK checkout and compare the PayPal CTA with the documented pay-wins behavior.
Test product
Merchant Test Kit
A sample product for checkout finality testing.
Quantity
1
- Subtotal
- Shipping
- Tax
- Total
Merchant configuration
Choose two independent signals
The order signal is sent at
payment_source.paypal.experience_context.user_action.
“Not set” omits the field or query parameter entirely.
Document prediction
Expected checkout behavior
- Resolved order signal
- Resolved SDK signal
- ModXO result
- Expected PayPal CTA
- Merchant capture
What did PayPal show?
Live checkout
Pay with PayPal
Loading the selected PayPal JS SDK…
Order captured
Order:
Status:
Transaction:
Claim verification
All nine input combinations
A true Continue flow returns here to a merchant review page without capture. All affirmative combinations capture as soon as PayPal approval returns.
Order user_action |
SDK commit |
Expected result | Expected CTA | Capture point | Observed CTA |
|---|
Exact integration diagnostics
JS SDK script URL
Expected SDK-derived /checkoutnow parameters
Orders V2 create payload
What this merchant verifies
Runtime claim checklist
- Independent inputs: the SDK URL and Orders payload are built separately and displayed above.
-
Defaults: omitting
user_actionresolves to Continue; omittingcommitresolves to true. - Pay wins: all nine combinations have a prediction and a place to record the CTA actually observed in PayPal.
-
Intent is separate: every order keeps
intent: CAPTUREwhile only the finality signals change. - True Continue behavior: approval returns to a merchant review page; only its Place Order button calls capture.