LC and credit card processing

Richard Miller wow at together.net
Mon Feb 25 19:32:35 EST 2013


All I want to do is capture the cc data as it comes off the card's 
stripe (as Colin says... converted into simple data through Rev), 
encrypt this data, then send it somewhere for processing and deposit 
into my account... with a result returned. I'd prefer avoiding any 
additional setup or coding (such as the need for server processing on my 
end). I don't care if it costs more to keep it simple. My application is 
not cost sensitive.

Will Stripe fit this bill? I can't quite tell after an initial review of 
the site.

Thanks.
Richard






On 2/25/13 7:06 PM, Andrew Kluthe wrote:
> I do not believe so. It's not the best solution for everyone, but it was
> the most *painless* solution I have used.
>
> Andrew
>
> On Mon, Feb 25, 2013 at 4:51 PM, Magicgate Software - Skip Kimpel <
> skip at magicgate.com> wrote:
>
>> But can Stripe integrate with card swiping hardware and provide the
>> merchant with the "card present" rate?
>>
>> SKIP
>>
>>
>> On Mon, Feb 25, 2013 at 5:48 PM, Andrew Kluthe <andrew at ctech.me> wrote:
>>
>>> That's the benefit of using Stripe in this situation. Stripe takes the
>>> place of a traditional gateway/processor/merchant account setup.
>>>
>>>  From their FAQ,
>>>
>>> Why is Stripe better than the other options I'm
>>> considering?<https://stripe.com/us/help/faq#why-is-stripe-better>
>>>> Glad you asked! Here are some reasons that others have chosen Stripe:
>>>>
>>>>     - Stripe is the only payments service you'll need. You won't need to
>>>>     find and work with a separate merchant account provider, gateway,
>>>>     subscriptions manager, or any other piece of the legacy payments
>>> industry
>>>>     puzzle.
>>>>
>>>>
>>>>     - An elegant, powerful API makes it quick and easy to integrate with
>>>>     Stripe. (See what developers are saying<
>>> https://twitter.com/#!/search/stripe%20api>
>>>>     .)
>>>>
>>>>
>>>>     - Complete freedom to create the payment experience you want—your
>> site
>>>>     or app, your workflow, your brand.
>>>>
>>>>
>>>>     - You can charge your users however you want: one-time purchases,
>>>>     subscriptions, metered billing, and event-based charges are all
>>>>     straightforward with our flexible API.
>>>>
>>>>
>>>>     - Competitive, crystal-clear pricing. We charge you one rate for
>> each
>>>>     successful transaction. There are no additional charges for failed
>>>>     transactions, American Express cards, international cards, stored
>>> cards, or
>>>>     recurring payments. It's easy to understand, easy to project, and
>>> without
>>>>     any surprises. (More about pricing <https://stripe.com/help/pricing
>>>> .)
>>>>
>>>>
>>>>     - We shoulder the PCI compliance burden by ensuring that you never
>>>>     need to handle sensitive card data. (Learn more about PCI and our
>>>>     approach <https://stripe.com/us/help/faq#pci-compliance>.)
>>>>
>>>>
>>>>     - Rapid help from real people. Jump into our real-time community
>> chat<
>>> https://stripe.com/chat> for
>>>>     immediate assistance from Stripe staff and our growing community of
>>> users,
>>>>     or email us <https://stripe.com/help/contact> for a fast, personal
>>>>     response.
>>>>
>>>> <https://stripe.com/us/help/faq#why-is-stripe-better>
>>> On Mon, Feb 25, 2013 at 4:41 PM, Mark Talluto <userev at canelasoftware.com
>>>> wrote:
>>>> On Feb 25, 2013, at 1:00 PM, Colin Holgate <coiin at verizon.net> wrote:
>>>>
>>>>> Credit card swipers just act like a keyboard input. You would listen
>>> for
>>>> the keys being pressed, build up the data, then when the return
>> character
>>>> comes in you process the text.
>>>>>
>>>>> On Feb 25, 2013, at 3:40 PM, Richard Miller <wow at together.net>
>> wrote:
>>>>>> I need a way to process a swiped credit card through Rev. The user
>> is
>>>> interacting via a touch screen (no keyboard or mouse). Just need to
>>> process
>>>> the card info... no address info. The card swipe unit is attached to a
>>>> portable Windows device which connects to the web via wireless (in
>>> public),
>>>> so the whole process must be secure.
>>>>
>>>>
>>>> There is a bit more to credit card processing if you want to be PCI
>>>> compliant.  In short, the swiper would provide you an encrypted
>>>> transaction.  You then pass this on to a PCI compliant processor.  They
>>> can
>>>> decrypt the record and respond to you with a yes or no on the
>>> transaction.
>>>>   You need to have a gateway to a processor and a merchant account to
>>>> receive the funds.
>>>>
>>>>
>>>> Best regards,
>>>>
>>>> Mark Talluto
>>>> canelasoftware.com
>>>>
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Andrew Kluthe
>>> andrew at ctech.me
>>> _______________________________________________
>>> use-livecode mailing list
>>> use-livecode at lists.runrev.com
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>
>





More information about the use-livecode mailing list