Wow! Thank you for sharing your startup. I see what you're doing and it's really a brilliant idea - it would work very well for payment funnels where consumers trust the brand.

I don't see any developer documentation though - is this intentional, or did I miss the link somewhere?

Is that intentional - heck no! It's a massive and glaring omission in our offering!

No but seriously, I'm banging away at documentation right now - the problem is it wasn't clear what exactly we needed to document until we launched and got the deluge of customer feedback that we've now gotten. It's now become clear that we're missing some critical features (for a lot of people) and that's it's not clear how to integrate it. Live and learn!

Essentially though, for 1 to 1 payments, you'll just sign up, sync your bank account, and you'll get a JS snippet and an HTML div. Put those on your site, feed the JS a payment amount, and when someone clicks the button - they'll pay, and you'll get the money. Then, at the end of the payment, you'll get a payment ID that you can store and use our entirely undocumented API to retrieve information you need later.

Hey, I just tried signing up and the site says I need to enter a referrer. Any chance you could let me see what this is like?

Use the code "LAUNCH"

Hey, I'm wondering if Knox integrates with Key Bank? Thanks

What am I using to login with my bank? Yodlee?

Nope - our own custom API that is way faster and (in our opinion) way safer. NOT to say Yodlee isn't safe, we just think we're safer.

Well, I'm sorry to say, you don't look safer. The URL changes from knoxpayments to paidez which looks super fraud-y! And you're not using good SSL certs. You do realize that you are requesting bank account logins from all your users? I couldn't find any information on your web site to help me determine if I should give you my online banking credentials.

I agree, we've done a pretty bad job of explaining and presenting ourselves thus far.

I'm not making any excuses, but we spent the last year building, speeding up, and securing the engine that handles the connections to bank accounts and the system to process and guarantee "good funds" ACH payments. We had an opportunity to go to Launch 2014, and even though the front end presentation of everything to the user was, in a word, "fucked", we made the decision to go and do the best we could to make it usable. This thread alone has helped me find a lot of the "anxiety" points people are having, and the customers I talk to everyday are getting me more. You'll see Knox back on HN soon with a much, much improvement experience.

How do your payments work? ACH or something else? Do you explain it anywhere?

It's ACH - there are some FAQS on knoxpayments.com/about.html

so who does the fraud detection? knoxpayments?

We do fraud detection on top of the fraud detection your bank AND the US banking system already do.

Nice! How can end users be confident their username/password for their banking site will be kept between them and their bank? (I'd be reluctant to enter those anywhere other than the bank's own site.)

As you should be! We're working really hard on educating our users at the point of purchase, but we do a meh job right now. However, users who are able to understand that we don't store any of your information convert at a very high rate.

Do you have any data on conversion rates? I imagine they would tank through the floor if you're asking a customer to turn over their online banking credentials.

Nope! Conversions are pretty good, same abandonment as CC's right now, and it's rising as we get our UX better. People hate inputting their CC information, and when they've heard of Knox at least 1 time before, they're way more likely to convert than using a CC. However, first time users are about the same conversion as CC's in our betas.

Hey, why don't you use HTTPS by default and your signup is in another domain (paidez.com)?

The Paidez thing is embarassing - we re-branded really fast and couldn't move all the services over before we launched. We're working on it now, but it sucks.

What do you mean about the HTTPS? We load ALL our content via SSL, do you mean knoxpayments.com isn't automatically loaded with SSL? There's nothing secure on it I guess, but even that should be for consistency.

Our payment process requires SSL end to end encryption, but are you suggesting that having Knox Payments not load with SSL by default it looks bad?

If I've missed something more important please tell me - if there's something (other than the atrocious switching of URLs) that is making you nervous, I NEED to fix it!

Are you able to take visa/mastercard?

We are not - we sync directly with people's online banking to make ACH payments without asking people to know their account and routing number.

Does that mean you require their bank account login info? If not how do you access enough infor for ACH?

That's the one!

Is posible to integrate into a IOS App?

We're building that SDK now - tommy at knoxpayments.com I can tell you more about it and see if it makes sense for what you're building.

Anything on the roadmap for Android?

RIGHT after iOS, could be a couple months though :/