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 Money Center Web Service​

The Money Center Web Service exposes a set of application program interfaces (APIs) that enables a way to send corporate transaction operations with addenda to the JHA SmartPay Platform from 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 Money Center API’s.

  • Process ACH Ability to process credit, debit and same day credit ACH transactions into a NACHA file.
  • Associate Customer Ability to add customer information to a transaction for reporting.
  • Custom Field Data Allows each transaction to have up to three fields of customized information for reporting.
  • Custom Description Allows a custom description to be associated with each transaction.
  • Addenda Transactions Allows for corporate ACH transactions to contain supplemental information through CTX and CCD+.
  • Settlement Report Generates a report of transaction settlement statuses for each merchant and location.

Data Elements​

Required Data Elements

There are some elements contained within AuthorizeMoneyCenterTransaction that 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 – The entityId is a unique identifier that is systematically generated when the merchant is newly installed on the EPS system. It is also referred to as the Merchant ID or MID.
  • owner entityId – The owner entityId is a unique identifier that is systematically generated when the entity is newly installed on the EPS system. Owner entity id also refers to as the Financial ID or Partner.
  • locationId – The locationId is a unique identifier for each location (account) set up under a merchant. Merchants 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.

Optional Data Elements​

The elements below are user-defined unique identifiers that reference a specific account or customer that has already been set up using the PaymentVault Web Services methods, RegisterAccount and RegisterCustomer. Those values, if available, can assist in retrieving the AccountNumber and RoutingNumber if not provided in the request. In addition, the AccountType value will be retrieved at the same time and will override any value included in the request for this element.

These elements are required when an AccountNumber is not provided and are designated with a ‘Y*’ in the required column.

note

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

  • customerNumber – The Customer Number is a unique identifier for each customer that is registered.
  • accountReferenceId – The Account Reference Id is a unique identifier for a specific account that is registered for a customer.

Same Day ACH Requirements​

  • OperationType - Per Nacha rules, Same Day ACH Credit (SDCredit) and Debit (SDSale) transactions cannot exceed $1,000,000 (1 Million).

Data Returned Limitation​

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

“The message was TR0l -The amount of data you requested exceeds system limitations and cannot be processed. Reduce the input range and submit your request again.”

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.