Bit Bayou
-
Posts
338 -
Joined
-
Last visited
-
Days Won
2
Posts posted by Bit Bayou
-
-
Well the quick / easy idea for using Twilio for automated payments appears to be a no go at the moment...
Unfortunately Twilio is not a PCI-compliant application platform, so we would advise against using our services in any situation where that is a requirement.
It is one of our long-term goals to be able to accomodate these use cases, but regretfully there is nothing in the short-term which will support it.
-
We considered doing this with Twilio, or a native Asterisk server for making payments by phone, verifying orders (Call the customer, ask them to enter a code into the order form), and more. We haven't had time to fully vet things, but Twilio appears to be a very useful service.
I may have to look in to payments by phone, using Twilio.
I'll be in contact with them, to verify the security enabled and offered by their service, to see if this is a recommended option. Will go from there!
-
I'm not sure, will consider further... Twilio makes it pretty easy though https://www.twilio.com/voice/api
-
if i will understan your idea .
if a (new order was placed/Service Activated/new ticket/ ect ... ) a TXT message is sent to the admin phone via external API .
I was considering this option, but was also wondering if there would be any other useful options?
Verified account registration? Though email does that.
I don't know?
-
Thought I'd share a notable, recent find!
PRINCIPLES OF MOBILE SITE DESIGN whitepaper published by Google, April 2014.
https://www.google.com/think/multiscreen/whitepaper-sitedesign.html
- Michael, Daniel B and Blesta Addons
-
3
-
I'm tossing around a few ideas for a cool and useful extension to start working on.
One of the areas I've been working in lately is text messaging and automated voice prompts / calls.
I would not incorporate a huge server side component in to the picture, but is there any interest in these features for an available extension in Blesta?
It would probably be through a 3rd party API, which may have its own charges associated per message and/or per minute, but there are a lot of possible options when looking down such roads.
Just wanting to get a community opinion and maybe some ideas on how these features could maybe be implemented and actually be useful?
-
Have we abandoned this topic already? I'm not here to blame anyone, point fingers, or none of that!
I'd just like to see either the stripe.js method as an available option or at least discuss and address the reasons why it won't / can't be?
Should this be pursued as a 3rd party add on option? Let me know!
-
Stripe has multiple methods for integration. Why would anyone just assume it's using stripe.js?
I really don't see the big deal with documenting it to make everyone happy, it seems simple enough, but I also don't get the witch hunt here.
If you didn't know before, you know now.
I realize the mistake of assuming there, and I was one of them in this case (Though as a local, small business, the gateway hasn't been used yet because my clients mostly prefer check payments).
Stripe does a great deal of advertising of saying how easy it is to accept credit cards and be compliant! I was following this story line (since it's their website, their gateway, etc).
I'm not sure about any witch hunt here either, I was simply trying to clarify this information since it was brought up and being discussed. I do agree it could be documented better, but I usually only glance at those when there's a problem with the system...
I do know now, and I could absolutely get behind a version of this gateway that does use their Strip.js library since they claim all I need to do with that is use an SSL certificate!
-
Also found at https://stripe.com/us/help/faq#my-pci-requirements
Anyone involved with the processing, transmission, or storage of credit card data must comply with the Payment Card Industry Data Security Standards (PCI DSS). Stripe makes it easy to do so:
Serve your payment page over SSL, i.e., the page's web address should begin with "https", not "http".Use Stripe.js or Checkout to accept payment information and transmit it directly to Stripe's servers.This sounds awesome! Just get an SSL Certificate, use Stripe, and I can accept Credit Cards without much else hassle!
But that's apparently not the case in Blesta, which is not advertised, and people are being critical about those who read this FAQ answer, and still didn't know any better
-
Yes, and that goes for other payment modules that Blesta is offering as well.
What integration method is used by each module and what the consequences are may not be sufficiently clear.
I think most smaller providers are better off with the non-merchant integrations all major processors offer.
Even if that means less pretty, less integrated payment pages.
I can understand the argument that it would be the same for any other merchant gateway (module) as well... But here's what most are reading (found at https://stripe.com/us/features#seamless-security)
No-hassle security & compliance
By using any of Stripe’s client libraries, such as Stripe.js for the web or the mobile APIs, you’re automatically compliant with the strictest PCI requirements.No sensitive data hits your servers, saving you hours of security headaches.The whole [quick/easy] selling point behind Stripe here is the you’re automatically compliant with the strictest PCI requirements and now the general attitude here that people should know better-- "better" being the opposite of what is advertised directly on their website
-
OK, and I am still required to have all of the other PCI compliance requirements? I was liking Stripe in the fact they did most of that for me! Is this not correct?
I apologize for the double post, but I want to readdress your attention here because I think this is where the most confusion is coming from? I have nothing stored on my server, except for the Blesta configured information. Are all of the compliance requirements still required, as discussed for legal compliance? I know it's recommended, but in the most basic legal / technical terms, is it?
-
I want to say this topic came up once, but I don't remember if there was ever anything figured out?
Many new TLDs are becoming available, and I'd like to start offering them too! Is there any update on the Namecheap module to include more TLD options, or maybe just leave a blank text box where I can fill in the selected choice?
Just looking for an update on this! Thanks!
-
Blesta will not store the card number in that case. Blesta has to store some card information, though. This includes the card type, last 4 of the card, and expiration date. This is required so that Blesta can send card expiration notices to clients, identify the card to the user for proper selection, and process refunds and voids.
OK, and I am still required to have all of the other PCI compliance requirements? I was liking Stripe in the fact they did most of that for me! Is this not correct?
-
If you check "Store Card Information Offsite" when configuring Strip in Blesta, Blesta will not store card details locally.
To Clarify:
I have this checked. Yet, Blesta still lets clients set up a Payment Account and store their credit card information. This information is not stored on my server? Stripe saves that for me, so I can then bill them later, correct? Therefore, none of the credit card data is stored on my server?
-
-
I added an info box toward the bottom above the currency listings for Bitpay in the documentation here - http://docs.blesta.com/display/user/Bitpay
Yeah, I was referring to a link in Blesta itself to those specific docs...
If you've used DirectAdmin before, the Help link at the top of each page is a link to the Docs for the section you're in...
Like if you're creating a new user in DA and click Help, it doesn't just take you to the home page of the help center, it directs you to the New User section of the help center! So there's no searching here or there for this section or that, the link is prominent on every page, and takes you directly to the information you need!
-
Have you tried using the Tab key?
I'll give it a shot. I'm for what ever works the best! I just thought I'd share my first experience to maybe help develop and fine tune it some more!
-
We stopped shipping Blesta with Google Checkout. We have not implemented a Google Wallet gateway, as some have reported that Google was not friendly to accepting payments for hosting providers.
My module is probably from an older version then.. Oh well.
Yeah, I've seen a few "Fly by night" companies using Google Wallet and then disappear as quickly as they appeared! It seems to be a good service, but Google needs to change their policies a bit for it to really work in this industry.
-
I use NodePing with some html/css trickery to make it kinda fit. Still have to work on it a bit.
I'm still a fan of uptimerobot because of the free pricing option.. but I do like how you integrated yours in to the website!
-
I wish I had more design freedom, like background images instead of just color... but I'm liking this so far!
-
once I get my hands on a KS-2 from KimSufi (Seems impossible!!)
I've been kind of wary about Atom processors in my servers for performance reasons... Have you done any load tests on these before? I might look in to one for a dev box though, I like their prices for something to at least try out!
-
Sure, you can let Blesta work it out... or set it yourself, if so desired
-
Oh! In case you want to keep the Blesta logo, but not white... app/views/client/bootstrap/images/logo-color.png Is a colorful version
-
Nginx Rewrite
in Support
Posted
Happy to see another member from the great state of Louisiana!
I've done a lot of work in Apache, but I have used tools like http://winginx.com/en/htaccess that help convert .htaccess Apache files in to the proper configuration for nginx