The design choice that matters most is the one you don't see: every card is entered on the bank's own hosted page. Everything else follows from that.
Customers type card details on NAB's hosted payment page. The bank returns a token for saved cards; Transiqe stores the token, the last four digits and the expiry, never the card number or security code. This keeps you and Transiqe in the lightest PCI DSS category.
Transiqe never holds funds. Card payments settle from your merchant facility to your bank account under your own agreement with NAB. If Transiqe disappeared tomorrow, your money would still be in your account.
Your gateway passwords and the Xero connection tokens are encrypted with AES-256-GCM before they're stored, and decrypted only in memory when a request to the bank or Xero is made.
Transiqe asks for the minimum Xero permissions: read contacts and invoices, record payments. It never creates or edits invoices, and you can disconnect it from inside Xero at any time.
Customers sign in with single-use links that expire after seven days. There are no customer passwords to leak. Business logins use hashed passwords and expiring sessions.
The amount charged always comes from the invoice as recorded from Xero, never from a link or a form field, so a modified link cannot underpay an invoice. Returns from the bank's page are signed and checked before anything is recorded.
Transiqe runs on Australian cloud infrastructure with encrypted backups. An audit log records every connection change, payment, refund and autopay decision per business, and you can see every email we sent on your behalf in your outbox. Questions about a security review, or a disclosure to make? Write to security@transiqe.com.
transiqe