<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Frames,</p>
<p>Putting UCC bank details on a poster would be a perfectly
suitable solution and would be very easy to implement - that
solves any actual problems we might potentially have.</p>
<p>As for technical failures, well, it is an experiment for that
purpose, and we will have to see how it works out in practise. If
you could get your hands on a device to test cheaply or for free,
it would no doubt be useful and I'd be happy to play around with
it even if it never became widely used in the club.</p>
<p>Considering that the primary concern is the cost, secondly the
effort required by committee to activate the account, having a
free device would solve at least half of the problem.<br>
</p>
<p>Being able to take card is indeed cool. Although, having thought
more about it myself, taking online payments is actually more
useful and would allow people to manage their dispense credit and
memberships online themselves. (Part of my longer term goal to
eliminate paper membership forms altogether, muahahaha!).<br>
</p>
<p>Anyway, if you could borrow a device for testing then that would
be great.<br>
</p>
<p>Kind regards,</p>
<p>[FVP]<br>
</p>
<br>
<div class="moz-cite-prefix">On 15/05/18 16:23, Frames wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5095340b-f921-fe76-a3c2-0f367701268c@ucc.asn.au">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>@Felix:<br>
Where were your thoughts on my point from before:<br>
<br>
Why don't we just stick our BSB and Account number on a poster ,
and people can open their banking app/website,<br>
and do a transfer witnessed by a door member, with their user ID
in the transaction description.<br>
Then the door member can add money on dispense, including the
"via bank transfer" in the description.<br>
And then when it comes to doing checking, <br>
the treasurer can just grep our bank statement, grep the coke
logs, and diff them.<br>
<br>
I mean it is a couple of extra steps over the ideal system, but
it isn't many.<br>
And it is free.<br>
and it basically has no technical failures compared to my
experience of PayPal here.<br>
</p>
<p>But anyway having a system that takes a card is cool.<br>
And adventures in payment APIs is a good educational experience.</p>
<p>I might be able to borrow a paypal here to use for testing and
setting up a system.<br>
That we could jeep for at least 6 months. Possibly with an
option to buy it for cheap if it works out.<br>
Do you want me to look into that?<br>
<br>
Kind Regards<br>
Frames</p>
<br>
<div dir="auto"><br>
</div>
<br>
<div class="moz-cite-prefix">On 15/05/2018 4:06 PM, Felix von
Perger wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5257e7c8-cff6-0649-8746-e281db065ba8@ucc.asn.au">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
An update on the pricings and information after doing more
research and talking to Mint payments for an hour yesterday.<br>
<br>
With regards to app integration, my main concern was whether it
could be integrated seamlessly enough into another app that you
do not need any user interaction (in other words, a setup with a
raspberry pi wouldn't necessarily require a touchscreen nor
direct user input). In this case it seems like Square would be
non-ideal.<br>
<br>
Essentially, Mint can't offer us any cheaper rates than the
following:<br>
<ul>
<li>Card reader is $300 to buy the device, no monthly fees
thereafter</li>
<ul>
<li>For every paypass (NFC/contactless) transaction, a flat
rate of 1% applies</li>
<li>For every EFTPOS (card + PIN and select "savings"), a
fixed price of 16.5c per transaction applies</li>
</ul>
<li>For online payments via their web payment gateway (ie. can
be integrated into the website)</li>
<ul>
<li>Costs $30/month to use</li>
<li>25c per online transaction, irrespective of payment
method</li>
</ul>
<li>APIs</li>
<ul>
<li>It is possible to seamlessly integrate the card reader
API into a separate app (ie. to avoid having to see/touch
their app when doing payments, good for dispense
integration)</li>
<li>Web integration (online payments) is possible with a
secure hosted payments page</li>
<li>No card details need to be stored by us<br>
</li>
</ul>
</ul>
<p>Supposing that the card reader is too expensive for this
experiment, Paypal and Square offer more affordable solutions
in the short term.</p>
<p>Square (see pricing <a moz-do-not-send="true"
href="https://squareup.com/au#section-b">here</a>):<br>
</p>
<ul>
<li>Card reader costs $59</li>
<ul>
<li>1.9% on all card transactions involving the card reader
(as far as I can tell)</li>
<li>Main downside to this is that the card reader has no
keypad; for card+PIN transactions, you must enter the PIN
code on the Android/iOS device rather than on the card
reader</li>
<li>Theoretically most people who have cards also have
paypass so it might not be necessary<br>
</li>
</ul>
<li>Online payments, virtual terminal & manually entered
card details in POS app<br>
</li>
<ul>
<li>2.2% flat rate</li>
</ul>
<li>APIs</li>
<ul>
<li>Card reader integration available (can write custom POS
apps; again dispense integration)</li>
<ul>
<li>However note that one must still enter PIN codes on
the app, which is not ideal</li>
<li>Anyone have experience <br>
</li>
</ul>
<li>Web integration possible using Square APIs (no out of
the box solutions available from Square, it seems, so we
must write that ourselves)</li>
<li>Unknown about card details, presumably we don't touch
them<br>
</li>
</ul>
</ul>
Paypal's <a moz-do-not-send="true"
href="https://www.paypal.com/au/webapps/mpp/paypal-seller-fees">pricing
structure</a> is similar:<br>
<ul>
<li>Paypal Here card reader costs $100 outright, no monthly
fees<br>
</li>
<ul>
<li>1.95% flat rate on all transactions</li>
<li>Card reader has buttons, don't need to enter anything on
app<br>
</li>
</ul>
<li>Online payments (presumably applies for both payments with
a paypal account and card payments)<br>
</li>
<ul>
<li>2.6% flat rate + 30c per transaction</li>
</ul>
<li>APIs</li>
<ul>
<li>Can write custom POS apps to use card reader</li>
<li>Web integration available using all kinds of existing
frontends that redirect to a hosted payment gateway; we
can also write our own frontend if we want.</li>
</ul>
</ul>
<p>[FVP]<br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
List Archives: <a class="moz-txt-link-freetext" href="http://lists.ucc.gu.uwa.edu.au/pipermail/committee" moz-do-not-send="true">http://lists.ucc.gu.uwa.edu.au/pipermail/committee</a></pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
List Archives: <a class="moz-txt-link-freetext" href="http://lists.ucc.gu.uwa.edu.au/pipermail/committee">http://lists.ucc.gu.uwa.edu.au/pipermail/committee</a></pre>
</blockquote>
<br>
</body>
</html>