I checked the docs on Jack Henry's website and it didn't show any information on how to use it on your website for banking. How do I get started using it in my website so that users can have an online banking experience. Can someone provide me some links that tell how to use Jack Henry on my website?
Assuming you're talking about the Digital Toolkit, that requires access to the Banno digital banking platform.
Ordinarily, financial institutions (e.g., banks and credit unions, the typical clients of Jack Henry) are the ones who use Banno to offer digital banking to their customers and members. If you're working directly with a bank or a credit union that has Banno, their Banno administrator should be able to help you with access to API credentials.
Notably, we also offer developers access to the Digital Toolkit via our demo institution (which is named Garden). Please review our Accessing the Digital Toolkit guide. That guide covers these topics related to the Digital Toolkit and our demo institution:
Signing up for a developer account
Creating a test user
Generating an External Application
Configuring a plugin
By the way, we also highly recommend registering for the monthly Toolkit Meetup where we answer technical Q&A from the audience: https://www.jackhenry.com/resources/events
Related
I am trying to automatize our cloud licenses assignment and permissions and I've done good progress with Office 365 and BIM 360 (for the permission per project part).
We are now planning to roll-out BIM 360 Design to many users (100+) and with our current 15 licenses, it's already quite complicated to manage assignment via Autodesk CEP panel. Thus, I'm trying to find informations on an API that could be used to manage users license assigment, similar to what we can do here: https://manage.autodesk.com/cep/#user-management
If assignment cannot be changed via an API, a report with current assignments could be a good start so I can have some reconciliation done on the side...
Anyone have an idea how to achieve this?
Unfortunately the BIM 360 APIs that are now publicly available focus on the management of project users. There's no endpoint for licensing purposes at the moment.
For assignment reporting or other BIM360 Design issues please visit our forum - questions on SO is not attended to by the relevant teams.
We recently submitted our Add-in for approval to be available on AppSource/Office Store and failed approval. Some of the feedback and policies make sense and we have addressed those items. However, there are a few policies that I'm not sure how to address and looking for guidance.
Policy 7.1 & 7.16 are about the supportURL not being publicly available and requiring Sign-in. Our add-in is not a general user add-in but targeted to Enterprise Customers of our Platform. They are provided a login for our support site so is this not sufficient? Do we really need a public url for an add-in targeted to Enterprise Customers?
As I was writing this I found the following link and wanted to make sure this was still valid and the same guidance for my scenario: App Submission - Help/Support Link Requirement
Policy 11.3 are about the Start-up experience needs to engage the user and show value proposition. Our users are Enterprise Users and have signed up for platform in which we will already guide them to use the Excel Add-in. Since they already know the value proposition from our sales team is there a way that this can be handled in our scenario without needing an explicit startup video or wizard walk through of app features?
Yes, this must be a public URL. The support link in your Seller Dashboard listing appears on the AppSource website so must be publicly available. It can be a link to your main website / or a contact page on your main website.
Have you seen the documentation on submitting Enterprise add-ins? This outlines which policies are not applicable when submitting an add-in which targets larger organizations and enterprises. It also explains how to declare, via test notes, that you are submitting an Enterprise add-in.
We are developing a Word Web Add-In that will be used exclusively by our customers rather than the general public. Customers will need to log into the Add-In in order to use it with credentials we supply. My question is, is this Add-In ok to be distributed via the Office Store? Will it fall foul of the validation process if its functionality is not publicly available ? Obviously, we can supply credentials to the verification team at Microsoft in order to get the app published.
If this is a problem, how do ISVs distribute Web Add-Ins to customers external to their organisation (i.e. Without Sharepoint or Office Admin Centre)?
This model is supported via the Office Store - this blog post on add-ins which target organizations and enterprises rather than consumers may be of interest to you.
Please ensure that your add-in description clearly states the need for an additional account, as well as supplying test credentials for the validation team to use.
Who writes on chip EMV application that communicates with terminal?
Are those developed by entities like VISA, Mastercard and given to issuing bank or the card issuing bank develops it and loads onto chip
In most simple terms,
Card manufacturers manufacture card and also installs operating system and applet ( if java - open platform).
Card issuers personalize these cards( I guess you know what will be there in an emv card).
After personalization, card is ready to use.
Anyone who wrote EMV application (either native or javacard applet) and pass the payment scheme certification (functional or security), he could sell his product.
The general idea is that the application developed have to pass the mandated certification test before going to the market and carrying the payment scheme brand.
There is a specification (ISO/IEC 7816-4) which specifies the protocol of an EMV card. It is on the net. Just google emvco and you would find them. The specification is complicated and takes time to understand. Here is a youtube channel
https://youtu.be/iWg8EBhsfjY
explaining the specification in a simple way. Especially for beginner. Check it out if you are interested.
Myself mendy, i am designing web application, The business required to integrate payment gateway. I searched on site regarding the flow but i could not get much info on MSDN. I want to make payment gateway using SSL and 3rd party merchant account. How can i do it ? some info regarding payment gateway could guid me to start developing the component.
You'll need to hook up with somebody like PayPal to process your payments. They will provide you with documentation and possibly a library to access their service.
Note that your payment processor is not necessarily the same company as your merchant account.
I'm assuming you wish to integrate with a payment gateway, not write your own?
If so, the answer is that it depends on the gateway that you intend to use. Each has their own API.
We use Iridium Corp for our products in the UK - they provide a bunch of .net components that you can just call from your code. Paypal will provide a well-documented API. So will some of the other big ones.
If you want some tips, you could look at some of the open-source shopping carts, which all have code to integrate to many of the big payment gateways.
Hope that helps...
Jake.
You should give wepay.com a try. There is now a C# SDK available with a few example here: http://bradoyler.com/post/29357874298/wepaysdk