Skip to main content
Version: 3.2

Flow

The target retrieves a remoteAction created by the source, changes its status, processes the request using the payment application, saves the result with the request, and transmits it to the paypercloud backoffice while changing the status to PROCESSED.

Sequence diagram​

Statuses and transitions​

  • [1] CREATED: The remote-action is created (by the source) and is ready to be sent to the target (terminal).
  • [100] PENDING: The remote-action has been pushed to the target, and is waiting for processing..
  • [200] INPROGRESS: The remote-action has been retrieved by the target and is being processed.
  • [300] PROCESSED: An remote-action is processed by the target and is queued for backoffice’s post processing .
  • any COMPLETED: The post processing is completed and the flow is finished successfully.
    • [1000] COMPLETED_WITH_SUCCESS: The remote-action was successfully processed.
    • [1050] COMPLETED_WITH_WARNING: The remote-action was processed with warnings (e.g.: receipt printing failed, gift card partial payment).
  • [400] ABORTED: The remote-action was cancelled by the user (payment failed, aborted ... )
    • [1400] ABORT_COMPLETED: The aborted remote-action was post-processed.
  • [500] CANCELED: The remote-action was manually cancelled by the source.
    • [1500] CANCEL_COMPLETED: The cancelled remote-action was post-processed.
  • [410] TIMEOUT: The remote-action has not been processed in time (future use).
    • [1410] TIMEOUT_COMPLETED: The timeout remote-action was post-processed.