...
The
...
possible
...
transitions
...
a
...
payment
...
is
...
able
...
to
...
be
...
part
...
of,
...
may
...
be
...
split
...
into
...
a
...
number
...
of
...
overall
...
steps:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
To
...
get
...
an
...
overview
...
of
...
valid
...
transitions,
...
see
...
the
...
following
...
diagram.
...
Please note, from all state it is possible to enter the error state, and from the error state it is possible to return to another state. This is not shown in this diagram.
The green arrows indicate transitions initiated by our business processes. This covers requesting a cancellation, a capture or a refund. In order to support to be able to enter the do_auth state again, it is also possible to request an authorization.
The red solid arrows indicate transitions initiated by our business logic (by means of requesting authorization, cancellation, capture or refund) but performed by the payment gateway.
The red dashed arrows indicate transitions initiated by the payment gateway. These transitions happens when the communication is a-synchronous and thus the response arrive 'later', not coupled directly to the previous request.
| Section |
|---|
| Column |
|---|
Authorization stepsdoAuthorizewhen a payment is created, it is always created with this status. This indicates that the payment should be validated and possible the amount reserved.
The payment will either be picked by Rator logic initiating the authorization, or it may be requested cancelled. authorizeSentWhen the authorization request is sent to the payment gateway, the actual communication may be delayed. In this case the payment gateway will indicate this with this state.
The payment will stay in this state until the payment gateway receives information about the next state. authorizedThe authorization request is processed and the money is reserved. This will be reflected financially in the Rator system by creating appropriate detail lines.
The payment will stay in this state until business logic or users request either a cancellation or a capture. rejectedThe authorization request is processed but the money could not be reserved. This could be caused by missing funds, wrong credentials, etc. This will be reflected financially in the Rator system by possible creating appropriate detail lines that will revert any previously created detail lines.
The payment is no longer active. In case a new authorization is needed, a new payment must be initiated. |
| Column |
|---|
Cancellation stepsdoCancelThe ongoing authorization is requested to be cancelled.
The payment will be picked up by Rator logic that will initiate the actual cancellation. cancelSentWhen the cancellation request is sent to the payment gateway, the actual communication may be delayed. In this case the payment gateway will indicate this with this state.
The payment will stay in this state until the payment gateway receives information about the next state. cancelledThe cancellation request is processed and the previous authorization is cancelled. This will be reflected financially in the Rator system by possible creating appropriate detail lines that will revert any previously created detail lines.
The payment is no longer active. In case a new authorization is needed, a new payment must be initiated. |
| Column |
|---|
Capture stepsdoCaptureThe previous authorization is requested to be captured.
The payment will be picked up by Rator logic that will initiate the actual capture. captureSentWhen the capture request is sent to the payment gateway, the actual communication may be delayed. In this case the payment gateway will indicate this with this state.
The payment will stay in this state until the payment gateway receives information about the next state. capturedThe capture request is processed and the previous authorization is fulfilled.
The payment will in most cases never leave this state, so effectively the payment is considered completed. However, business logic or users may request the payment to be refunded, as well as the third party may initiate the payment to be withdrawn. rejectedThe capture request is processed but the money could not be transferred. This could be caused by account being terminated or blocked, or the previous authorization has expired. This will be reflected financially in the Rator system by creating appropriate detail lines that will revert any previously created detail lines.
The payment is no longer active. In case a new authorization and capture is needed, a new payment must be initiated. withdrawnThe capture request is completed, but the third party have initiated the payment to be withdrawn. This will be reflected financially in the Rator system by creating appropriate detail lines that will revert any previously created detail lines.
The payment is no longer active. In case a new authorization and capture is needed, a new payment must be initiated. |
| Column |
|---|
Refund stepsdoRefundThe previous captured is requested to be refunded.
The payment will be picked up by Rator logic that will initiate the actual refund. refundSentWhen the refund request is sent to the payment gateway, the actual communication may be delayed. In this case the payment gateway will indicate this with this state.
The payment will stay in this state until the payment gateway receives information about the next state. refundedThe refund request is processed and completed successfully. |
|