x

Square / Tiphaus API errors

We are experiencing issues with the integration between Square and Tiphaus. I’d caution you to look this over if you utilize both systems to pay your employees, and you’re not tip pooling.

When a check is opened by Server A, they become the owner of that check (found on the check as “Owned by”). If Server B is logged in (I.e. forgets to log out) when Server A closes that check and takes payment, the logged in server becomes the “Collected by” name on the check. 

The integration pulls the “Collected by” data and not the “Owned by” data to Tiphaus. This will warrant the need to do a manual correction of whom the check is attributed to in Tiphaus before correct tips can be assessed. 

The best way to verify this is to check a sample day’s Net Sales per employee in Square and comparing them to the same day’s sales breakdown in Tiphaus. If these numbers are not the same, you’re in the same boat as us. 

Long story short, Square and Tiphaus have verified this problem to exist, but the correct API that would allow this connection to be made correctly is private and won’t be shared from the Square IT team to outside vendors. So - can anyone else confirm that this is a problem for them?

580 Views
Message 1 of 2
Report
1 Best Answer
Square Community Moderator

Best Answer

Hey @Krobartender,

 

Thanks for reaching out. Your APIs need to give us the "owned by" person in the orders or payments API, but they do not.

 

 

MayaP
Square Community Moderator
Sign in and click Mark as Best Answer if my reply answers your question

View Best Answer >

394 Views
Message 2 of 2
Report
1 REPLY 1
Square Community Moderator

Best Answer

Hey @Krobartender,

 

Thanks for reaching out. Your APIs need to give us the "owned by" person in the orders or payments API, but they do not.

 

 

MayaP
Square Community Moderator
Sign in and click Mark as Best Answer if my reply answers your question
395 Views
Message 2 of 2
Report