Page Comparison

The possible transitions a payment is able to be part of, may be split into a number of overall steps:
- authorization, where the payment is validated and the amount is possible reserved on the customer account.
- capture, where the reserved amount is actually transferred from customer account to the client account.
- cancel, where an authorization may be cancelled.
- refund, where a captured payment may be refunded (initiated by Rator).
- withdrawal, where a captured payment may be withdrawn (initiated by external party).

To get an overview of valid transitions, see the following diagram.

{gliffy:name=Account Payment capture status overview|version=25}

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.

h3. Authorization steps

h5. doAuthorize
when 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.

h5. authorizeSent
When 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.

h5. authorized
The authorization request is processed and the money is reserved. 
The payment will only be picked up by logic, requesting either a cancellation or a capture.

h5. rejected
The authorization request is processed but the money could not be reserved. This could be caused by missing funds, wrong credentials, etc.
The payment is no longer active. In case a new authorization is needed, a new payment must be initiated.

h3. Cancellation steps

h5. doCancel

h5. cancelSent
h5. cancelled

h3. Capture steps
h5. doCapture
h5. captureSent
h5. captured
h5. rejected
h5. withdrawn

h3. Refund steps
h5. doRefund
h5. refundSent
h5. refunded