Simulate incoming payment review case
Create one synthetic incoming-payment review case for sandbox, public-test, and Playground use. The created case feeds the existing transaction review flow: inspect it via GET /transactions or GET /transactions/, reject it via POST /transactions//reject, and, when allowed, approve it via POST /transactions//approve. This route is create-only, does not expose internal compliance-engine internals, and does not become a second transaction API family. Scenario semantics are frozen to sanctions_hit (sanctioned external sender/counterparty, decisionMode=reject_only), sender_kyc_not_approved (sender compliance status fails receiver acceptance, decisionMode=reject_only), and counterparty_info_incomplete (manual review required because required counterparty fields are missing, decisionMode=manual_review_required). For counterparty_info_incomplete, the created review case later exposes missingRequiredFields = [senderFullLegalName, senderCountryCode, senderDateOfBirthOrRegistrationId, purposeOfPayment] on the existing transaction review reads.
Authorizations
Integration-key Basic Auth (clientId:clientSecret) as documented in docs/public/AUTHENTICATION.md.
Headers
Optional platform scope selector for sandbox multitenant/internal compatibility. Basic-auth integration requests normally omit this header because platform context is derived from credentials. If supplied, it must be a UUIDv4 value.
^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-4[0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}$Body
Exact request contract for creating one synthetic incoming-payment review case. Additional properties are not allowed.
Receiver customer identifier for the synthetic incoming payment review case.
1Frozen sandbox scenario selector. sanctions_hit means the external sender/counterparty is sanctioned. sender_kyc_not_approved means the external sending VASP or FI supplied a sender compliance status that fails receiver-platform acceptance. counterparty_info_incomplete means manual review is required because required counterparty fields are missing; the created review case later exposes missingRequiredFields = [senderFullLegalName, senderCountryCode, senderDateOfBirthOrRegistrationId, purposeOfPayment] through the existing transaction review reads.
sanctions_hit, sender_kyc_not_approved, counterparty_info_incomplete Positive incoming amount in minor units.
x >= 1Incoming payment currency as an uppercase 3-letter code.
^[A-Z]{3}$Response
Synthetic incoming-payment review case created. Use the returned transactionId with the existing transaction review APIs.
Bounded create acknowledgement for the synthetic incoming-payment review case. This is not a second transaction detail model; continue on the existing transaction review APIs using transactionId.
Canonical follow-up identifier for GET /transactions/{transactionId} and POST /transactions/{transactionId}/reject.
1Receiver customer targeted by the simulation.
1Frozen sandbox scenario applied to the created review case.
sanctions_hit, sender_kyc_not_approved, counterparty_info_incomplete Fixed transaction type for this sandbox simulation route.
INCOMING Fixed initial review status for the created incoming payment case.
PENDING Always true because the synthetic case is created in review-required state.
true ISO timestamp for when the synthetic review case was created.