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 SmartPay Manager Web Service​

The SmartPay Manager Web Service exposes a set of application program interfaces (APIs) that enables a way to retrieve and send data with the JHA SmartPay Platform for very specific use cases if your organization is also leveraging RiskForce. 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 SmartPay Manager API’s.

List of features

  • Hold All Credits Report – Will create a list of all merchants and locations in a hold all credits status.
  • Check21 Report – Ability to retrieve transaction information based on a transaction ID.
  • Check21 Adjustment – Ability to request the adjustment of a check21 transaction amount based on the original reference number.
  • Suspended Transactions Report – Will create a report of all suspended transactions created in the last 90 days.
  • Force Approve Transaction – Ability to Force Approve a single transaction in a suspended status.
  • Force Void Transaction – Ability to Force Void a single transaction in the suspended or approved status.
  • SmartDetect Report – Ability to create a report showing total SmartDetect requests for merchants and locations.

Web Services​

A web service is an interface between different web-based application sources that provides them with the ability to communicate with each other without any custom coding or knowledge of each other’s systems. They can “share business logic, data and processes through a programmatic interface across a network.” Enterprise Payment Solutions (EPS) web services are used to send transaction operations to EPS via the internet.

note

The information contained in this document is based on the use of SOAP and/or WCFStorm. Results may vary if any other source application is used.

Data Elements​

Required Data Elements​

Some elements contained within SmartPay Manager methods are required and the applicable data will be provided to you by Enterprise Payment Solutions when your merchant entity has been set up. These required elements are shown below.

  • storeId – A unique user ID systematically generated by EPS upon installing a new web service user. The StoreId can be unique to each individual merchant, or a master StoreId can be assigned at the partner/owner level.
  • storeKey – A unique password systematically generated by EPS upon installing a new web service user. The password corresponds with the StoreId above.
  • EntityId – This is the ID of an entity that has been identified as an Owning Entity. This method cannot be executed at the individual merchant level.
  • MerchantId – This 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 (MID) or Customer ID.

Optional Data Elements​

The elements below are user-defined values that are not required to submit the request.

  • RequestDate – The date in which the request is being made. The element must either be null or contain a date (YYYY-MM-DD) but cannot be blank. If you chose to use this element, please use the current date.
  • RequestId – This is a user defined value used to identify the request. No value is required for this element. It can be blank, but it cannot be null.
note

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

System Requirements​

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.