benbyf

Just had a quick look and they're very similar. I'm using: $intent = $payment->paymentCheckout($description); Instead of $payment->render(); The $intent variable then returns an array of the [0] Stripe form and [1] Intent Id. https://github.com/benbyford/PaymentStripeIntents/blob/master/PaymentStripeIntents.module#L138 This is because you may want to store only the Intent or just the form. Like to spend some more time with this module soon, so there will probably better Readme and additions soon.

I can look at getting them more closely integrated when I’m back next week from holidays. I’ve not used the padloper module and tbh it might be better that they integrate it or do their own as I’m not selling this as a premium module, just my own version of the new Stripe Intents API

Hey @MarcoPLY did you follow the readme? The render method currently doesn’t do anything in this module.

Ah ok thanks, probably to do with the schema of the site profile I’m installing then. Will try starting from a default profile and overwriting to get where I was. Thanks

Very confused about this, did an installation, wanted to change profiles so deleted EVERYTHING and reinstalled and getting this very strange error: Anyone come across this, not happened before. I use serverpilot.com and digitalocean with Ubuntu 14 boxes installing 3.0.123

More implementations Ajax modal version: : New page version:

Example implementation: Info: So this is very much an ALPHA version of what I hope turns into a swiss armory knife payment module. Currently you are able to take payments with the payments form or cross browser payments button (Apple Pay etc). Please read implementation details here and consider contributing https://github.com/benbyford/PaymentStripeIntents TODO: Add subscription functionality Add customer functionality More testing and code clean up More usage examples anything else?

What i have so far: https://github.com/benbyford/PaymentStripeIntents/blob/master/PaymentStripeIntents.module

Module's currently operating with this basic functionality: Take credit card details and confirm with Stripe Add js styling in moudles settings for Stripe Elements Form. So you can change how the form is displayed. On return -> POST successful transaction id, name and email to relative url of your choice Things I'm looking to add: Ability to POST successful values via AJAX to relative url of your choice. Add CrossBrowserButton functionality - e.g. pay with apple pay button Option to disable CrossBrowserButton if not required Save Stripe Intent variables in session to be accessed by templates e.g. save amount, and currency in session to be used by module and / or template. Need to do something like this anyway as Stripe CrossBrowserButton doesn't take the same Intent information (see previous post ☝️). Integration of module with PaymentModule - quite a bit of duplication currently here, so need to do some work to string the new module closer to payments module. Let me know what else might be useful?!

OK done some digging and found this absolutely stupid thing in their API: intents work with StripeElements menaing you can create a payment intent and supply that intent id to a form to start taking the payment, you can then use their API to step through the payment process using the language of your choice (pretty much) – I'm looking to implement both a PHP and JS implementation into my module. HOWEVER: if you want to use the cross browser payments button (e.g. pay with apply pay, google pay) then you have to create a new payment request to that js api, e.g. doesnt work with your pre-authed intent id... I've taken this up with them and they say: I consider this a massive oversight as surely the payment intents arethe beginning of ANY interaction with the StripAPI, in this case not. Anyway, will continue to work on this one to implement as much as possible.

I've been working on this a looks like it WILL require a change, as it now requires you update your payment journey to use PaymentIntentions, e.g. setting a intent to pay at the beginning of any payment checkout before actually requesting card information, address, email etc etc... I'm currently having to do this for my clients and adding support for Stripe Elements. Love this to be robust butI'm simply not a very good backend dev so muddling through it. Will release what I have when it's done hopefully in a week.

Think i'm miss understanding the conversion between curl in the terminal and curl in php. Looking at the below and wondered how to set the -u. Is it setting a CURLOPT_USERPWD header? Or more complex than that? https://stripe.com/docs/payments/checkout/migration#client-products-server-code curl https://api.stripe.com/v1/customers \ -u sk_test_4eC39HqLyjWDarjtT1zdp7dc: \ -d email="{{STRIPE_EMAIL}}" \ -d source="{{STRIPE_TOKEN}}"

Trying to rework my Stripe implementation to get up-to-date with the latest regulation changes and wanted to use wireHttp instead of simply curl, but couldnt work out at all how to add a user password along with the request.

Hi! Been doing some basic Twilio implementation for a client to enable them to automatically send text messages to registered users on page publish. As an upshot, I thought I would strip out the site specific work and stick up on github here: https://github.com/benbyford/TwilioChannels This modules pulls in the Twilio APi and enables you to send SMS messages from your front or backend. Send SMS message Truncate message to single message character limit Auto-select number from range of numbers depending on $To number country of origin–this enables you to send messages with a local number to that user if one added to the config. Templates usage: $twilio = $modules->get("TwilioChannels"); $twilio->sendSMS($toNumber, $message);

Will be publishing my store soon @MateThemes so might be easier to join forces? I also agree with @wbmnfktr not sure patreon is the right place for this.