Submit completed money-flow transactions for a session
POST/transaction/push
Submit one or more completed purchases for a k-ID session. Each event records what was bought, what it cost, and whether the charge went through. Use this endpoint after a purchase completes, including each renewal of a recurring one.
Set status to failed for a charge that was attempted and did not
complete, so a parent can tell the two apart.
Events are processed independently. The response carries a per-event status:
accepted- the purchase was recorded. Resubmitting an event whoseidwas already accepted is a safe no-op: it counts asacceptedagain and is not recorded twice, so retries after a network failure won't double-count.rejected- the purchase failed validation; thereasonidentifies which rule.
The whole batch is rejected when the session does not exist or is revoked.
Request
Responses
- 200
- 400
Batch processed. Per-event statuses indicate acceptance.
Invalid request - the response body's error field carries a
specific code (e.g. INVALID_INPUT, NOT_FOUND,
FEATURE_DISABLED).