# Transfer Status

The status of a Travel Rule transfer evolves as it moves through different stages of processing. Each status reflects a specific point in the transfer lifecycle. These status updates help track progress, identify bottlenecks.

### Sample Flow

1\.  User →  Originator VASP A: Initiates Withdrawal Request\
2\.  Originator VASP A →  Ospree: Create Travel Rule Transfer\
3\.  Ospree →  Beneficiary VASP B: Send Travel Rule Message\
4\.  Beneficiary VASP B →  Ospree: Respond. Action "accept" or "reject"\
5\.  Ospree →  Originator VASP A: Pass Beneficiary Response\
\
**If "Accepted"**\
6a. Originator VASP A →  Initiate Blockchain Transaction\
6b. Originator VASP A →  Ospree: Update Transfer respond action "complete"\
\
**If “Rejected” without retry**\
6c. Originator VASP A →  Customer: Notify Customer of Rejection\
6d. Originator VASP A →  End: Cancel Withdrawal\
\
**If “Rejected” with retry**\
6e. Originator VASP A →  Originator VASP A: Repair Travel Rule Data\
6f. Originator VASP A →  Ospree: Update Transfer. Action "repair"\
6g. Ospree →  Beneficiary VASP B: Re-send Updated Travel Rule Message\
6h. Beneficiary VASP B →  Ospree: Respond. Action “accept”\
6i. Ospree →  Originator VASP A: Forward New Response\
6j. Originator VASP A →  Initiate Blockchain Transaction\
6k. Originator VASP A →  Ospree: Update Transfer. Action "complete"

<figure><img src="https://4249894339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQg7OS46Jha8pRGgGDSDo%2Fuploads%2FvuKtecrr9RCY83JHCqxK%2FVASP%20Database%20(5).png?alt=media&#x26;token=268b8ca2-bc60-422c-ad3e-b270f1d15375" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="153.62109375">Status</th><th>Description</th></tr></thead><tbody><tr><td>INITIATED</td><td>The transfer request is sent to the beneficiary VASP using the Create Transfer endpoint.</td></tr><tr><td>REVIEW</td><td>The transfer request is being reviewed by the beneficiary VASP.</td></tr><tr><td>CANCELED</td><td>The originator VASP canceled the transfer request using the Action Transfer endpoint.</td></tr><tr><td>REPAIR</td><td>The originator VASP updates the transfer request based on the rejection reason using the Action Transfer endpoint.</td></tr><tr><td>REJECTED</td><td>The beneficiary VASP rejected the originator VASP’s request, providing a reason and indicating whether a retry is allowed, using the Action Transfer endpoint.</td></tr><tr><td>ACCEPTED</td><td>The beneficiary VASP accepted the transfer request, allowing the originator VASP to proceed with executing the crypto transaction using the Action Transfer endpoint.</td></tr><tr><td>COMPLETED</td><td>The originator VASP has completed the execution of the crypto transaction using the Action Transfer endpoint.</td></tr></tbody></table>