Who cares about developer experience? Genuinely asking, because I’m a developer too and I certainly don’t care. What we care about is solving the actual problem of payments with the downstream companies.

▲

jazzyjackson 7 hours ago | parent | next [-]

DX = developers not shooting themselves in the foot and making it impossible to cancel my free trial because my account got deleted but the autopay didn't

fewers bugs = happier customers not getting charged for shit they didn't agree to be charged for

▲

agreeahmed 6 hours ago | parent [-]

Basically this. The existing integration paradigm for payments, at its worst, feels like a warehouse filled with footguns on the floor with the lights turned off. Esp for newer developers who are used to more modern devexes which explicitly try to take reasoning about complex state transitions off of your plate.

	▲	scott_w 4 hours ago \| parent [-]
		100% This. I remember joining a billing team that assumed calls to Braintree succeed or fail, so everything was just calling the API as though it was a local function call. It was great fun debugging the twice annual incidents where the API returned a HTTP500 but charged the customer and created the recurring subscription anyway. Not to forget we had to scream at them for 6 months to implement 3DS2 on top of their Subscriptions API. Turns out we were the only users of it!

▲

poly2it 7 hours ago | parent | prev | next [-]

Stripe became dominant by improving developer experience, which cuts implementation costs.

▲

mcflyin619 7 hours ago | parent | prev | next [-]

I care about my own developer experience. If i can save a headache and some time integrating payments, I'm all for it.

▲

Scubabear68 7 hours ago | parent | prev [-]

“Well your payments platform doesn’t actually do payments, but the developer experience of doing nothing was flawless!”

Sorry for the snark, but been in payments a long time, and seen too much of this nonsense.

	▲	7 hours ago \| parent [-]
		[deleted]