Setting Up Remote Deposit Capture via Urban FT
This guide explains how to implement Remote Deposit Capture (RDC) with your system via Urban FT. Before implementing RDC, see the Remote Deposit Capture via Urban FT guide for general information on the user experience and use cases.
Result of setting up RDC via Urban FT
Account holders can take a photo of a physical check and deposit it via your mobile app.
Prerequisites
- SoFi Tech Solutions must perform setup steps to enable this feature to work with your system.
- You must obtain sponsor bank approval – the sponsor bank receives the Urban FT X9 file, settles the check, and sends return files back to Urban FT.
- You must establish a relationship with Urban FT and integrate the Urban FT SDK to capture check images.
- You must provide a way for Urban FT to reach your system for status updates.
- You must align on business rules Urban FT will use to approve or decline RDC deposits. Urban FT provides a standard set of business rules you can find in their client documentation, but you might also have business rules specific to your organization.
Workflows
These are the entities involved in setting up RDC via Urban FT:
- Account holder — Your customer, who has at least one account on your platform.
- Your system — Your mobile app or web page, which has a control to launch the remote check deposit process.
- SoFi Tech Solutions — The system that provides APIs for Urban FT to post, adjust, and return payments.
- Urban FT — The entity that provides intake and review of check images and creates the X-9 file and submits to your sponsor bank.
- Sponsor Bank — The financial institution you're partnering with to support this functionality. The Sponsor Bank submits the X-9 file to the Federal Reserve and receives return files that are passed back to Urban FT.
- Fed — The Federal Reserve; clears ACH transactions.
Use the following diagrams and corresponding steps to understand how to implement RDC via Urban FT:
Check capture and review workflow
sequenceDiagram
participant AH as Account holder
participant SYS as Your system
participant UFT as Urban FT
AH->>SYS: Requests check deposit
SYS->>UFT: Sends PRN
AH->>UFT: Captures check image and enters details
Note over UFT,AH: If capture fails
UFT-->>SYS: Capture error
SYS-->>AH: Prompt to retake
Note over UFT,AH: If capture succeeds
SYS-->>AH: Shows submission screen
AH->>UFT: Confirms and submits deposit
Note over AH,UFT: Outcome — Approved
UFT->>SYS: Approved
SYS->>AH: Emails final status
SYS->>SYS: Payment creation begins
Note over AH,UFT: Outcome — Manual review
UFT->>AH: Email — pending review
UFT->>UFT: Review Center recommendation
UFT->>SYS: Final status
SYS->>AH: Emails final status
Note over AH,UFT: Outcome — Rejected
UFT->>SYS: Rejected
SYS->>AH: Emails final status
This workflow shows the initial process for an account holder capturing and submitting a check via your system.
- In your system, an account holder requests to deposit a check.
- Your system provides the PRN to Urban FT via the Urban FT SDK.
- In your app, the account holder takes a picture of the front and back of the check they want to deposit and enters information related to the deposit.
- Urban FT captures the remote deposit using the check image SDK.
- If the image capture is unsuccessful, your system displays an error message to prompt the user to retake the photo.
- If the image capture is successful, continue these steps.
- Your system shows the account holder a submission screen.
- The account holder confirms and submits the deposit.
- Urban FT determines whether the check passes their predefined business rules and does one of three things:
- Approves the deposit.
- Flags the deposit for manual review. This triggers an email notification to the account holder that their deposit is pending additional review. In these cases, Urban FT's Review Center performs the review and returns the final recommendation.
- Rejects the deposit.
- Urban FT sends your system the status of the account holder's deposit.
- Your system sends the account holder an email notification communicating the final status of their deposit.
- If Urban FT approves the deposit, the payment creation workflow begins.
Payment creation workflow
This workflow shows what happens after Urban FT approves the deposit.
sequenceDiagram
participant AH as Account holder
participant SYS as Your system
participant UFT as Urban FT
participant STS as SoFi Tech Solutions
participant SB as Sponsor bank
participant FED as Fed
Note over UFT,STS: Create payment
UFT->>STS: POST/createPayment (check amount, hold days)
STS-->>UFT: POST/createPayment response
STS->>SYS: BPMT event
STS->>SYS: pmt webhook (amount, type, status)
Note over UFT,FED: Parallel — X-9 file process
UFT->>SB: Generates and sends X-9 file
SB->>FED: Forwards X-9 file
FED->>FED: Processes X-9 file
Note over SB,FED: After predefined days
SB->>SB: Receives funds from checkholder's bank
Note over SB,SYS: If funds cannot be received → Returns workflow
Note over STS,AH: After hold days expire
STS->>STS: Applies payment to available balance
STS->>SYS: expire_hold webhook
SYS->>AH: Notifies balance increase
- Urban FT calls the Create Payment endpoint to post a payment for the amount of the check to the account holder's account, with hold days based on your business rules configuration with Urban FT.
- SoFi Tech Solutions creates a payment with hold days on the account holder's account and returns the API response for Create Payment.
- SoFi Tech Solutions sends your system a
pmtevent webhook showing the payment amount, transaction type, and status. - At the same time, Urban FT starts the X-9 file process.
- Urban FT generates an X-9 file and sends it to the sponsor bank.
- The sponsor bank sends the X-9 file to the Fed.
- The Fed processes the X-9 file.
- After the predefined number of hold days has passed, the account holder's sponsor bank receives the funds from the checkholder's bank. If this is not possible, the Returns workflow begins.
- After the hold days expire, SoFi Tech Solutions applies the payment to the account holder's balance.
- SoFi Tech Solutions sends your system an
EXHD: expire_holdevent webhook showing the payment hold has expired. - Your system notifies the account holder of the increase in their available balance.
Returns workflow
This workflow shows what happens when a check bounces, triggering a return.
sequenceDiagram
participant AH as Account holder
participant SYS as Your system
participant UFT as Urban FT
participant STS as SoFi Tech Solutions
participant SB as Sponsor bank
participant FED as Fed
Note over FED,UFT: Check bounces — X-9 return
FED->>SB: Incoming X-9 return file
SB->>UFT: Forwards X-9 return file
UFT->>UFT: Receives X-9 return file
Note over UFT,STS: If original payment has been posted
UFT->>STS: POST/createAdjustment (reverse payment)
Note over UFT,STS: If original payment has not been posted
UFT->>STS: POST/expireHold
UFT->>STS: POST/createAdjustment (reverse payment)
Note over STS,AH: Balance update
STS->>STS: Decreases available balance
STS->>SYS: adjustment_event webhook
SYS->>AH: Notifies adjusted balance
- The check bounces.
- The Fed sends the sponsor bank an incoming X-9 return file for processing.
- The sponsor bank receives the X-9 return file and sends it to Urban FT.
- Urban FT receives the X-9 return file.
- If the original payment has been posted, Urban FT calls the Create Adjustment endpoint to create an adjustment to reverse the payment to the account holder's balance.
- If the original payment has not been posted:
- Urban FT calls the Expire Hold endpoint for SoFi Tech Solutions to expire the hold on the payment.
- Urban FT calls the Create Adjustment endpoint to create an adjustment to reverse the payment to the account holder's balance.
- SoFi Tech Solutions decreases the account holder's available balance and sends your system an
BADJ: adjevent webhook. - You notify the account holder of their adjusted balance.
Updated about 4 hours ago

