Skip to main content

Overview

About JHA SmartPay PlatformTM. Integrated Payments Platform that Supports Multiple Payment Channels.​

Owning the dynamic payments channel is getting more difficult with new competitors, new payment alternatives, and new end user expectations. But when you choose the JHA SmartPay Platform, you gain fully integrated solutions that support virtually every payment channel and the entire lifecycle of virtually every payment type. These industry-leading solutions can be implemented as a holistic payments ecosystem or as standalone solutions. And additional solutions can be easily added to support your evolving payments strategy and emerging payment channels. These solutions include.

  • JHA SmartPay Remote Deposit CompleteTM (RDC) - High-volume remote deposit capture with proofing and balancing services
  • JHA SmartPay Remote Deposit NowTM (RDN) - High-volume remote deposit capture with business-managed proofing and balancing
  • JHA SmartPay mRDCTM (Mobile Remote Deposit Complete) - Commercial mobile remote deposit capture solution built exclusively for businesses
  • JHA SmartPay ExpressTM - Payments portal for online payments and donations
  • JHA SmartPay Biller DirectTM - Electronic bill/invoice presentment and payment solution for billers
  • JHA SmartPay CardTM - Cost-effective card transaction processing for small and large merchants
  • JHA SmartPay ACHTM - Sophisticated bulk file or individual ACH transaction processing
  • JHA SmartPay ManagerTM - Intelligent administrative portal

About the JHA Remote Deposit Reporting Web Service​

The Remote Deposit Reporting Web Service exposes a set of application program interfaces (APIs) that enables a way to retrieve remote deposit batch and item information from the JHA SmartPay Platform for building custom reports and keeping deposit data current within your application. Enterprise Payment Solutions (EPS) robust APIs can be configured and deployed to offer highly scalable payment solutions for near-term needs, with the flexibility to quickly and seamlessly add payment options to support evolving business strategies and market demands. Following are the features that are available through the Remote Deposit Reporting API’s.

List of features

  • Batches Report - Ability to pull detailed information, including statuses, about a batch of remote deposit items.
  • Batch Events Report - Ability to pull specific event information (Created, Deposited etc.) that has occurred on a remote deposit batch.
  • Items Report - Ability to pull detailed information, including statuses, about an individual remote deposit check item.
  • Item Events Report - Ability to pull specific event information (Created, Rejected etc.) that has occurred on a remote deposit item.

Required and Optional Data Elements​

Required Data Elements​

Some elements contained within PaymentVault that are required and the applicable data will be provided to you by EPS when your merchant account has been set up. These required elements are shown below.

  • storeId – A unique user ID systematically generated by EPS upon installing a Web Service user. The storeId can be unique to each individual merchant, or a master storeId can be assigned at the reseller/owner level.
  • storeKey – A unique password systematically generated by EPS upon installing a Web Service user. The password corresponds with the storeId above.
  • entityId – The entityId is a unique identifier that is systematically generated when the merchant is installed on the EPS system. It is also referred to as the Merchant ID or MID.
  • LocationIds – The LocationIds element represents a list of one or more unique identifiers, one for each location (account) set up for a user, provided by EPS when an account has been set up. Users that process transactions for multiple accounts or use the same account for multiple purposes (i.e. building fund, donations, dues), will be assigned individual location IDs for each.
  • BinarySecurityToken - This is an access token that is generated via a request to an authentication endpoint. This access token will need to be submitted via the SecurityHeader portion of the header in each request. See the Authentication Guide for more info.
note

Only those fields required by the EPS system will de denoted by a ‘Y’ in the required column.

Optional Data Elements​

For some optional elements, if the element is included in the request, then a value must be provided by the user. This means that the element can be null but cannot be empty. These elements are listed below.

  • BatchStatus – This element represents the status (Open, Closed etc.) of a batch. If this element is not included in the request all statuses will be assumed.
  • BatchEventType – The BatchEventType element represents the different event steps or processes that a batch could go through. If this element is not included in the request all event types will be assumed.
  • IncludeImages – This element designates whether document images will be included in the response. If included in the request, valid values are: 0 = False; 1 = True. If null, no data will be returned.
  • ItemEventType – The ItemEventType element represents the events or processes through which a specific transaction goes. If this element is not included in the request all event types will be assumed.
  • ItemStatus / Status – This element represents the status of a specific transaction. If the element is not included in the request all item statuses will be assumed.

This document will make every effort to identify each of these element types within a method.

Data Returned Limitation​

Requests for data that exceeds 100k records will return a TR01 error response as displayed below.

“Server was unable to process request. ---> An exception of type System.ApplicationException was thrown. The message was TR01 - The amount of data you requested exceeds system limitations and cannot be processed. Reduce the input range and submit your request again.”

System Requirement​

Secure Sockets Layer (SSL) Implementation Required

Requests must be originated using HTTPS protocol. This requires requesting servers/users to use the Secure Socket Layer (SSL) for encrypted communication.

Support​

Contact Information

Questions regarding RDA Mobile Web Services or this interface guide may be addressed to: Telephone: (877) 433-3812