You're right, incumbent SIS/LMS vendors are rolling out AI features. We’ve studied (and, in my past life at Salesforce, helped build) some of them. What we keep hearing from IT teams is:
- Integration tax: Each module still lives in its own data model. Schools end up exporting CSVs or building Mule pipelines to reconcile SIS+LMS+CRM. Our agent sits on top of all sources with pre-built connectors and a unified schema, so coaches see enrollment + Canvas grades + attendance in one call (like in the Triage Center)
- Operational burden: Products like Data Cloud or Agentforce are powerful but need admin capacity that smaller schools just don’t have. We ship a default ruleset for advisors + prompt library so an advisor can be productive immediately.
- Cost creep: Several platforms meter GPT usage or require new AI licenses. We price per active student so budgeting is predictable, which is a big plus for universities and their unique budget cycles.
Curious if you’ve found pain points around data normalization especially (this is the hard, very custom part of our work right now). Happy to keep the discussion here for the benefit of others, and if you’d like to dive deeper my email is sadia@risely.ai
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.
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
Hi, Stripe's support keep telling us it is a a bank error.
According to stripe logs, a successful transaction has 3 steps: create a token (/v1/tokens), then the customer (/v1/customers) and finally generate the payment (/v1/charges). At the moment, all the transactions are falling when they receive the customer (/v1/customer). I am not sure what's causing the issue, I am requesting to talk to an engineer to get any response other than "talk to your bank" (we have talked to them 4 times already :(
Thanks for giving me the chance to clarify what's going on.
I don't see the payment intent endpoint listed here, which means you're not allowing for authentication challenges (SCA/PSD2). So it's possible the bank is denying the charge, but your flow isn't accounting for it if it's not using payment intents. See here for updating your implementation to account for SCA: https://stripe.com/docs/strong-customer-authentication/migra...
This was my first thought as well. OP, your symptoms sound very similar to an app I recently updated to support SCA - it was just dropping a portion of the payments.
We are using stripe's api in the frontend to generate a token and then it to our backend in order to generate the "customer" and the "charge". Our backend is on Rails so we are using stripe's ruby gem.
We should talk. I used to work with universities.