What are Tacit's payment programs integrations ?

Student and Corporate Payment Integrations

Tacit Payment Program Integrations

• Blackboard - cloud, need tender
• Blackboard Transact - on premise, need tender
• CBORD - need tender • Atrium
• TouchNet • Volante - need customer type

Location has to get an agreement from Blackboard to integrate. For each plan you can have a payment card rules. Meal plans are a form of gift cards for us. Each plan may or may not have tender.

Requirements for Student Payment plans 

1. What are the payment plan types? 

1. Inclining Balance

• No need to split payment

2. Declining Balance

• Supports splits payments
• User will be automatically pay additional amount with credit card or will be prompted to add credit is balance does not cover order total

3. Meal Plans

• Uses meals credits only, cannot split payments with separate payment type

4. Loyalty Points

• Dollar amounts can be paid for by redeeming loyalty points, split payments are available

 

2. What is the user authentication flow? 

• The user authentication flow is the way in which users will be able to sign in an access they payment plan

We have 3 authentication flow options:

1. SSO (Single Sign-On)
   1. Shibboleth
   2. OpenID
   3. Azure Active Directory
2. Email and Password
3. First name, Last name, Card number

• • This is considered the least secure option. Majority of available integrations prefer to go with SSO.

Integration with Azure Active Directory requires a setup of metadata, containing the user attributes which will be passed through authentication (e.g. card number, first name, last name, email, phone number).

Single Sign-On Flows 

Shibboleth Single sing-on flow 

OpenID Authentication Flow

 

Needed for the integration:

• student card number format

• key to decrypt the JWT token

• web URL (University's authentication page)

• redirectURL (upon successful authentication)

• sandbox environment (to test integration)

2. Would your prefer to have just the student card number or the whole set of data encrypted? 

There are 2 options the data can be passed:

1. Directly, without any encryption

2. Encrypted with the JWT token

1. the data is encrypted on the school’s side

2. passed to Tacit server as a token

3. decrypted and stored on Tacit server

4. the user doesn’t see the full card number, but only first or last 4 digits of it are displayed

• For data security purposes, the encryption option is preferred. The key to decrypt the token will be required from the school.
• Phone number will not be passed within a token, but will be collected from a user on the registration step.
• The example below outlines the set of metadata and the JSON structure to be used (example, but depends on the actual set of data per integration)

{"FirstName":"John", 

"LastName":"Smith", 

"Email":"[e-mail]", 

"CardNum":"12345678" }

In case the card balances can’t be retrieved (the card is lost / stolen / there’s network outage) • The user will receive the error message, prompting to register the student card again or select a different payment method.

• Alternatively, the school may opt-in to pass the student ID together with the student card number. If we have a student ID, in case the balances can’t be retrieved, the user will see a “Retrieve card balance” button, without having the need to re-register.
• This option is more complex and would require additional API’s to be provided by the school to associate the student ID and the card balances, and thus would be an additional development effort.

 

3. Do your payment types have discounts?

• A lot of student and employee payment plans provide customer with discounts if they are paying with their plans

• Discounts may also include tax exemptions on payments

• Tacit will need to know what type of discounts will apply to each payment tender (payment method)

 

UI/UX Requirements

1. Digital asset for the student card display on the app

• Format: jpeg, .png or original file
• Size: 276x174 px

2. Verbiage for message in case of a lost card/ network issues

Program Specification Checklist

Payment integration

• Blackboard - cloud
• Blackboard Transact - on premise
• CBORD • Atrium
• TouchNet
• Volante - need customer type

Payment plan types

• Inclining balance
• Declining balance
  • Split payments
• Meal plans
• Loyalty points

Authentication Flow

• SSO
  • Shibboleth
  • OpenID
  • Azure Active Directory

• Email & Password
• First name, Last name, Card number

Encryption

• Directly, without any encryption
• Encrypted with the JWT token Discounts

Discounts

• No Discounts
• Discount
• Tax Exemptions