¶ IngoPay API
¶ Overview
Straight-thru processing to any endpoint in the Ingo Payments Gateway for PCI-certified platforms.
¶ API Authentication
The IngoPay API utilizes HMAC Authentication. HMAC Authentication is a mechanism for calculating a message authentication code using a hash function in combination with a shared secret key between the two parties involved in sending and receiving the data (Front-end client and Back-end HTTP service). The main use for HMAC is to verify the integrity, authenticity, and identity of the message sender.
¶ The following is required to authenticate to any of the Ingo Instant Payments API methods.
Valid participant ID provided by Ingo Money
Valid Secret provided by Ingo Money
An HMAC signature must be generated and sent in the Authorization header; the data in the Authorization header will contain the username, signing algorithm, headers, and the signature
- A comprehensive packet of information on creating your HMAC authentication will be provided with the credentials listed above.
¶ Abstracts
| Abstract | Summary |
|---|---|
| Search the Ingo Money Biller/Payee database for support of a given customer account to be funded. | |
| Verify support for customer account data provided on a selected payment request. | |
| The risk platform supports two methods, Session & Score. The Session Method provides clients with session identifiers which enable risk assessment. | |
| Submit a request to push funds to a customer's account. | |
| Submit a request to pull funds from a customer's account. | |
| Receive status codes & descriptions by applicable API Method(s) to aid in definng & supporting your customer's experience. | |
| Receive timely detailed information regarding IngoPay API payment update activities. Only subscribe to events of interest for your program. |
¶ Permitted Character Set
