Skip to main content

Class UpdateDepositItemsRequest


Properties

NAMETYPELENGTHREQUIREDDESCRIPTIONEXAMPLES
PartnerIdInteger9YesThe Partner ID is a unique ID assigned by Ensenta specific to each setup within Ensenta’s platform and will be different for each environment (UAT and Production).

For more details, review the PartnerId parameter in Start Session request.
<PartnerId>8257</PartnerId>
LanguageIdInteger1YesSend integer 9<LanguageId>9</LanguageId>
DepositorIpAddressString45YesIP address of End-User (NOT calling web service). IPv4 or IPv6 are accepted.

This is optionally used to enable Geolocation functionality. Reach out to your Ensenta PM if there are any questions regarding Geolocation.
<DepositorIpAddress>
203.0.113.0
</DepositorIpAddress>
DeviceIdentifierStringN/AYesThe unique UUID generated for the phone.<DeviceIdentifier>
21d182e6-10b1-48e2-8c53-1b72674836c1
</DeviceIdentifier>
LocalDateTimeStringN/AYesDate and time where the device End-User is. For example:
  • 2018-08-08T08:43:52.000-07:00


Note: You must include the colon in the offset
<LocalDateTime>
2018-08-08T10:52:47.000-07:00
</LocalDateTime>
TimeZoneStringN/AYesTime zone of End-User.

Required Format: Timezone{space}UTC offset{space} Area/Location

Example: PDT -07:00 America/Los_Angeles

Differentiate Day light savings, for ex, send PST (Pacific Standard Time) or PDT (Pacific Daylight Time).

Note: Area/Location is optional.
<TimeZone>
PST -8:00 America/Redwood_Shores
</TimeZone>
AttributesAttribute[]YesAn array containing attributes for utilizing miscellaneous optional functionality that may be added to over time.

Attributes are defined Name/Value pairs. This is to support potential future functionality to easily expand on your integration.

There is no functionality available for this parameter at this time; pass the Name and Value parameters below as empty.

Note: You may have heard Ensenta make references to Attributes in the past; there is another type of Attributes named Account Holder Attributes which does have functionality available and is described below within the StartSession request. For more details, look at the AccountHolderAttributes parameter in StartSession request.
<Attributes>
<Attribute>
<Name></Name>
<Value></Value>
</Attribute>
</Attributes>
SessionStateIdString36YesThe session state id from the SessionStateID parameter returned in the StartSession response.<SessionStateId>
994be4fb-3dc5-4ceb-b13b-dccfd4c9768c
</SessionStateId>
SessionTokenString36YesThe session token from the SessionToken parameter returned in the StartSession response.<SessionToken>
52269818-4f3e-410c-87ad-1f5922f0b4d6
</SessionToken>
DepositBatchIdString36YesThe deposit batch id from the DepositBatchId parameter returned in the CreateDepositBatch response.<DepositBatchId>
9dae3f3a-d8b0-451e-88cc-ecc33dfefe48
</DepositBatchId>
DepositItemCorrectionsDepositItemCorrection[]YesContains the DepositItemCorrections details.

Contains the DepositItemCorrection details.
<DepositItemCorrections>
<DepositItemCorrection>
...
</DepositItemCorrection>
</DepositItemCorrections>
DepositItemStatusInteger2YesSend integer -1<DepositItemStatus>-1</DepositItemStatus>

Attribute

NAMETYPELENGTHREQUIREDDESCRIPTIONEXAMPLES
NameStringN/AYesNot applicable, leave empty.<Name></Name>
ValueStringN/AYesNot applicable, leave empty.<Value></Value>

DepositItemCorrection

NAMETYPELENGTHREQUIREDDESCRIPTIONEXAMPLES
ItemNumberInteger2YesSend integer 1<ItemNumber>1</ItemNumber>
AmountDecimal19YesIf the End-User updated the check amount, provide in decimal form.

If the End-User did not update the check amount, send the original amount submitted within the Amount parameter from the AddDepositItem request.
<Amount>2.11</Amount>
MicrString80NoLeave empty<Micr></Micr>
IsConfirmedBooleanN/ANoThis has been deprecated. Send boolean value of 'false'<IsConfirmed>true</IsConfirmed>
FixedRiskFactorIdsInt[]N/ANoLeave empty<FixedRiskFactorIds></FixedRiskFactorIds>
IsDeletedBooleanN/ANoSend “False”<IsDeleted>false</IsDeleted>
CheckImageCategoryIntegerN/AYesSend integer 1<CheckImageCategory>1</CheckImageCategory>
ImagePreprocessStateIntegerN/AYesSend integer 2<ImagePreprocessState>2</ImagePreprocessState>
FrontBase64ImageStringN/ANoIf the End-User retook the check images, this is the Base64 string of front image. Leave blank if the End-User did not retake the check images.

Note: If sending an image, both the front and back images should be sent, even if just replacing one.

Refer to the Mitek image guidelines document for details on formatting check images.
<FrontBase64Image>
<!— Base64 Image -->
</FrontBase64Image>
BackBase64ImageStringN/ANoIf the End-User retook the check images, this is the Base64 string of back image. Leave blank if the End-User did not retake the check images.

Note: If sending an image, both the front and back images should be sent, even if just replacing one.

Refer to the Mitek image guidelines document for details on formatting check images.
<BackBase64Image>
<!— Base64 Image -->
</BackBase64Image>

Examples

<UpdateDepositItems>
<request>
<PartnerId>8257</PartnerId>
<LanguageId>9</LanguageId>
<DepositorIpAddress>203.0.113.0</DepositorIpAddress>
<DeviceIdentifier>21d182e6-10b1-48e2-8c53-1b72674836c1</DeviceIdentifier>
<LocalDateTime>2018-08-08T08:45:58.000-07:00</LocalDateTime>
<TimeZone>PST -8:00 America/Redwood_Shores</TimeZone>
<Attributes>
<Attribute>
<Name></Name>
<Value></Value>
</Attribute>
</Attributes>
<SessionStateId>554196f0-02fb-438b-bd0a-9c07bed6f9f9</SessionStateId>
<SessionToken>1337417d-db57-4c17-8f37-41c12e5933cd</SessionToken>
<DepositBatchId>9dae3f3a-d8b0-451e-88cc-ecc33dfefe48</DepositBatchId>
<DepositItemCorrections>
<DepositItemCorrection>
<ItemNumber>1</ItemNumber>
<Amount>2.11</Amount>
<Micr></Micr>
<IsConfirmed>true</IsConfirmed>
<IsDeleted>false</IsDeleted>
<CheckImageCategory>1</CheckImageCategory>
<ImagePreprocessState>2</ImagePreprocessState>
<FrontBase64Image></FrontBase64Image>
<BackBase64Image></BackBase64Image>
</DepositItemCorrection>
</DepositItemCorrections>
<DepositItemStatus>-1</DepositItemStatus>
</request>
</UpdateDepositItems>