cityofaustin / atd-data-tech

Austin Transportation Data & Technology Services
17 stars 2 forks source link

Discovery: Citybase online payment system #7179

Closed moorerst closed 3 years ago

moorerst commented 3 years ago

Get understanding of how Citybase online payment system works for Banner's Payments.

Who should we meet with?

moorerst commented 3 years ago

@johnclary will make contact and provide introductions

moorerst commented 3 years ago

Mark C and Amber R are the contacts John could you set up a meeting so we can talk through this.

Yep that was at a very high level and at best

dianamartin commented 3 years ago

@moorerst Should we set-up the meeting on behalf of John since we're doing the discovery and invite him of course?

moorerst commented 3 years ago

meeting scheduled for 9/30. Per stakeholder the approximate number of transactions is 5-10/wk Banners have a different cost depending on the type of Banner (over the street, lamp post)

dianamartin commented 3 years ago

Meeting with CTM - discussion about CityBase

Discussion about Street Banner Program being interested

Attendees: Mark C, Jim M. (CityBase), John, Diana

Next program: RPP to do ePayments Annual permits, renewals, day passes (ad hoc purchases) No online payments

Designing the payments Passing the information Tracking what the person paid for

City is each service cost Ex. $140 of it

V/MC 1.85% AMX 2.2%

We need to discuss how to collect the fees

CityBase to write Statement of Work

Payment page that accepts an order

Back and Forth API conversation Create JSON string

Send to end point at CityBase

Call back to Knack - can't control how we receive the POST request Parse the response

Mark has the call back information that ATD needs

Knack has an API

Payment Confirmation screen

They get sent back, post back, sent directly back to Knack Knack would have to receive the API call

Could pass an off-token, that off token used in CityBase and authenticate an API request

Do share a "key", unique hash, use key to share to recreate the hash

Send custom parameters and get them back in the POST Design the information

J's Q: Post back - the web client? or back end server from CityBase (coming from city base's server) Configure that with a static token Whatever you send to CityBase will get send back

Can you install a certificate on CityBase's side? Will share a (secret/key), CTM saves it in the database. Uses that as a verification tool. API get hits from other things that aren't CityBase. Helping weed out the information.

Other ways to make it work with CityBase

CityBase Integrations

Lobbyist Payments- City Clerk's Office Hotel Tax System - taxes that hotels and short term rentals, they have to pay taxes HR is going live

5-9 other projects in total Public Works want to come on Other departments want to get on

Just recently Statement of Work, Austin Public Health

DTS will struggle with bandwidth too Need to tackle the real mechanics and go through the handshakes

BIG ONES

Statement of Work

Service fees for the credit cards Payment Types, ACH, Credit Cards What kind of integration

Library has a middle ware they run

They built a system they made in-house

Secret/Key - what the token looks like getting back from CityBase?

BEST PRACTICES

Talk to Finance as well to determine their preferences

moorerst commented 3 years ago

Follow up meeting scheduled 10/13 Closing this issue