Stripe | Integration Engineer | Berlin, Dublin, London, Madrid, Paris, or Remote | ONSITE, REMOTE, VISA
Stripe's Customer Engineering team in EMEA – working directly with the best-known and most technically complex companies in the world – needs tech-savvy, empathetic problem solvers to help design and deploy our user’s successful Stripe integrations.
We are looking for people who are comfortable in multiple programming languages, interested in working with our users, and delving into complex integration problems spanning time, currencies, and alternative payment methods.
We’re very keen to chat if you are:
* Confident and comfortable with customers. We're expecting to see customer facing roles in your past or present.
* A strong technical generalist. We come from a diverse set of backgrounds, but experience with full-stack development and software architecture patterns are critical to success in our roles.
* Comfortable with code-level debugging (Stripe code and user code).
* Intellectually curious, with great problem solving skills. You will be challenged to find inventive solutions to technical and non-technical restrictions on both sides of an engagement, at the intersection of people, engineering and payments.
According to [1] it is required and there's no other (documented) way to do it.
Ditto for stripe.createToken() [2].
In fact, there's no word in the docs on how to feed raw card data into the v3 at all.
So we had no choice but to use Stripe.card.createToken() from the v2, but then also use stripe.handleCardAction() from the v3 for confirmation... it's a mess. What did we miss?
beware of PCI compliance requirements [0] but you can either create a payment method explicitly [1] or include the card details when handling a card payment [2] `{payment_method_data: {card: {…}}}`
I am aware of [0], but unless I'm missing something neither of the methods allows creating a payment method on the client and then passing its ID to our backend to be executed and set up for 'future use'.
That's the flow we had with the v2 and that's what we can't replicate with the v3.
Sorry, I didn’t see the previous post. Different sources anyway, imho this one is a more complete analysis. I rewrote the original title since it was not informative enough ("A Remote iOS Bug”), and the subheading was too large to post (“apple wrote code to appease the chinese government ...it was buggy”). I don’t think the headline was misleading: the crash was absolutely related to the Taiwanese flag emoji censorship.
Just to clarify, the original submission headline was «iOS bug triggered by 🇹🇼 censorship». The emoji there had a literal rather than symbolic meaning.
Whilst some well-known experts have already agreed to share their ideas at this year's MonadLibre, we are still open for proposals. Please contact monadlibre@merchise.com
Stripe's Customer Engineering team in EMEA – working directly with the best-known and most technically complex companies in the world – needs tech-savvy, empathetic problem solvers to help design and deploy our user’s successful Stripe integrations.
We are looking for people who are comfortable in multiple programming languages, interested in working with our users, and delving into complex integration problems spanning time, currencies, and alternative payment methods.
We’re very keen to chat if you are:
* Confident and comfortable with customers. We're expecting to see customer facing roles in your past or present.
* A strong technical generalist. We come from a diverse set of backgrounds, but experience with full-stack development and software architecture patterns are critical to success in our roles.
* Comfortable with code-level debugging (Stripe code and user code).
* Empathetic, collaborative, communicative, consultative.
* Intellectually curious, with great problem solving skills. You will be challenged to find inventive solutions to technical and non-technical restrictions on both sides of an engagement, at the intersection of people, engineering and payments.
Please check out the Integration Engineer role on our jobs page: https://stripe.com/jobs/listing/integration-engineer-emea/22...
Have any questions about the above? Email me directly: lx+hn@stripe.com