Payment actions

Given a particular configuration the next_actions object is set on the tracker. This specifies the next action that must be executed to progress the state. For example:

{
  "intent": "CYBERSOURCE",
  "mode": "payment",
  "next_actions": {
    "CYBERSOURCE": {
      "kind": "GENERATE_CAPTURE_CONTEXT"
    }
  }
}

This means that to progress the tracker for a card payment (via Cybersource), the next action to be executed is GENERATE_CAPTURE_CONTEXT.

Executing actions requires running the Order endpoint with appropriate payloads. The client may run this endpoint repeatedly until no more actions remain. This is signified by the NO_OP action at which point the payment journey would be complete.

The response returns the updated tracker and the result of the action inside the action object. This is often necessary for preparing the payload for the subsequent action.

Reference

All payment actions are documented with examples under the Order API and Cancellation API reference.