Hacker News new | ask | show | jobs
by IdontRememberIt 2290 days ago
> We want to own the entire checkout experience

The less you see, the better. Being PCI DSS compliant (as soon as you see/store sensitive transaction data) is a pain...

1 comments

What I meant was, we don't want to redirect them to another website. I agree with what you mention.

Sorry if I wasn't clear.

You don’t have to redirect to another website. I recommend getting a better web developer because integration with Stripe can be completely seamless.
Stripe is starting to inject themselves into the transaction, turning more into Apple Pay by saying the charges API is deprecated

I think OP is just looking for something similar to Stripe. I’ve found Pin Payments to be pretty good. If they’d support ‘connect’ I’d migrate everything over to them

I believe you're talking about Stripe Checkout - which is totally optional and helps developers really quickly add a payment form to their site (like PayPal). I use Stripe on a number of my projects and at my startup and users never need to know "Stripe" exists unless I want them to. Disclosure: I am a former Stripe employee.
> Stripe is starting to inject themselves into the transaction, turning more into Apple Pay by saying the charges API is deprecated

That's not at all what is happening. Do you have any idea why they deprecated the charges API ?

All I know is I went with Stripe so I didn’t have to see the PayPal logo (or any logo) in my checkout process

You don’t have to confuse things with an intermediate brand to wait for a user to auth a transaction in their banking app, just leave the timer on the screen until they do it

> we don't want to redirect them to another website

As a security consultant and user, I would prefer actually seeing whoever processes my data for a few reasons:

- I know who gets my data; it is not sent to them in the background and one can only find out through legalese (if at all, since "a payment processor" is all you're legally obliged to say)

- Payment data processed by a third party is likely more secure than an average-sized web shop (even if you just proxy it, a hack can impact that but it couldn't impact paypal's security without messing with the URL, which the user could observe (and if you say "but you're a security dude" yeah, but I also teach others to do the same and I've seen companies train their users on the concept of a domain followed by a slash, it isn't hard))

- I know what many of those companies' security reputation is

- And I may know the general reputation of the company, e.g. PayPal has a rich history of issues with both merchants and users so I would rather go back and choose another option if possible