---
title: "Create a Remote Check Deposit"
method: POST
path: "/rdc/deposits"
tags: ["Remote Check Deposit (beta)"]
---

# Create a Remote Check Deposit

`POST /rdc/deposits`

Create a new deposit using remote deposit capture to an account

## Headers

- `Idempotency-Key` string

## Request body

- DepositPost — User provided request to submit an RDC
  - `account_id` string, uuid, required — The ID of the account
  - `back_image_id` string, uuid, required — ID of the uploaded image of the back of the check
  - `business_id` string, uuid — Unique ID for the business. Exactly one of `business_id` or `person_id` must be set.
  - `check_amount` integer, required — Amount on check in ISO 4217 minor currency units
  - `deposit_currency` string, required — ISO 4217 currency code for the deposit amount
  - `front_image_id` string, uuid, required — ID of the uploaded image of the front of the check
  - `metadata` Metadata — Optional field to store additional information about the resource. Intended to be used by the integrator to store non-sensitive data.
  - `person_id` string, uuid — Unique ID for the person. Exactly one of `person_id` or `business_id` must be set.
  - `tenant` string — The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.

## Response `201`

Successful creation of a deposit using remote deposit capture

- DepositGet — Deposit using remote deposit capture
  - `account_id` string, uuid, required — The ID of the account
  - `back_image_id` string, uuid, required — ID of the uploaded image of the back of the check
  - `business_id` string, uuid — Unique ID for the business. Exactly one of `business_id` or `person_id` must be set.
  - `check_amount` integer, required — Amount on check in ISO 4217 minor currency units
  - `deposit_currency` string, required — ISO 4217 currency code for the deposit amount
  - `front_image_id` string, uuid, required — ID of the uploaded image of the front of the check
  - `metadata` Metadata — Optional field to store additional information about the resource. Intended to be used by the integrator to store non-sensitive data.
  - `person_id` string, uuid — Unique ID for the person. Exactly one of `person_id` or `business_id` must be set.
  - `tenant` string — The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces.
  - `creation_time` string, date-time
  - `date_captured` string, date-time, required — Date the deposit was captured, in RFC 3339 format
  - `date_processed` string, date-time, required — Date the deposit was processed, in RFC 3339 format
  - `deposit_amount` integer, required — Amount deposited in ISO 4217 minor currency units
  - `file_loc_identifier` string, nullable — Identifier of the ICL file this deposit was transmitted in, if any
  - `id` string, uuid, required — Remote Check Deposit ID
  - `last_updated_time` string, date-time
  - `matching_declined_check` string[] — IDs of other deposits, already rejected, that appear to match this check (same amount, MICR, and check number). Advisory only; does not block this deposit.
  - `matching_pending_check` string[] — IDs of other deposits, currently pending, that appear to match this check (same amount, MICR, and check number). Advisory only; does not block this deposit.
  - `matching_submitted_check` string[] — IDs of other deposits, already submitted, that appear to match this check (same amount, MICR, and check number). Advisory only; does not block this deposit.
  - `ocr_account_number` string — Account number of the issuer of the check, included if OCR is successful
  - `ocr_check_number` string — The unique check number for this check in the checkbook, included if OCR is successful and there is a check number on the check
  - `ocr_routing_number` string — Routing number of the issuing bank, included if OCR is successful
  - `status` 'FAILED' | 'MANUAL_POST_REJECTED' | 'PENDING' | 'REJECTED' | 'RETURNED' | 'SUBMITTED', required — The status of the deposit
  - `transaction_id` string, uuid — The ID of the transaction associated with this deposit
  - `vendor_info` union — The information provided to Synctera from the vendor. Interpretation of this object is up to the client.
    - object
      - `content_type` 'application/json', required — Describes the content-type encoding received from the vendor
      - `json` object, required — Data representation in JSON
      - `vendor` string, required
    - object
      - `content_type` 'text/xml', required — Describes the content-type encoding received from the vendor
      - `vendor` string, required
      - `xml` string, required — Data representaion in XML

## Other responses

- `400` — BadRequest
- `401` — Unauthorized
- `404` — Resource not found
- `422` — The submitted deposit has been flagged as a duplicate submission

---

[API](https://skmtc.net/synctera/apis/synctera-api.md) · [All operations](https://skmtc.net/synctera/apis/synctera-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/synctera/synctera-api/revisions/b0d812e6cdd0/schema)