Settings and activity
14 results found
-
20 votes
An error occurred while saving the comment An error occurred while saving the comment Tim Rutter commentedReally should of had WebAuthn support years ago.
We use YubiKeys' for WebAuthn authentication with all other online services, even internal sites.Apple also uses WebAuthn for Passkey which was announced Jun 6th 2022 at WWDC 2022.
Information links
https://www.yubico.com/authentication-standards/webauthn/
https://support.apple.com/en-au/102195#About-the-security-of-passkeysDeveloper Info
https://developers.yubico.com/WebAuthn/
https://developer.apple.com/documentation/authenticationservices/public-private_key_authentication/supporting_passkeys/Tim Rutter supported this idea · -
245 votes
Hi community, we've released our first update to history and notes of new invoicing, where you can now view more detail of changes such as where an issue or due date has been altered or the amount of your invoice is changed. There's more improvements for this space coming soon and I'll keep you up to date with these, here.
Tim Rutter supported this idea · -
237 votes
Hi everyone, we assure you that our leadership and those that can make a difference to the new invoicing experience are aware of your comments and all the feedback of how we can improve this space for all our customers.
Product ideas here have been specifically designed so we can ensure we have a channel and are getting our customers feedback to the teams and people to consider, plan and prioritise change to impact and make a positive difference to our users experience in all our products. For example - every week all the feedback (every one of the comments) goes to the new invoicing team and has been read by leadership including our CPTO.
Individual personal details have been removed from commentary in this thread as it goes against part of our Community Guidelines.There are really important reasons why we must go forward with sunsetting classic invoicing…
Tim Rutter supported this idea · -
7 votes
An error occurred while saving the comment Tim Rutter commentedHi we have stopped using the GoCardless integration and moved our repeating invoicing to another service.
Xero does not even support moving the Direct Debit charge date ahead of the due date, as our current platform supports and where to find any large opperator do this a norma practise.
Tim Rutter supported this idea · -
5 votes
An error occurred while saving the comment Tim Rutter commentedI was using the old 'GoCardless for Xero' integration, Which is not longer under deleopment by GoCardless.
The new GoCardless as a payment method integration is developed direcly by Xero.
Now a long list of non working fetature since we switch over, which was recommended by Xero.
Soy you may need to look elsewhere, as Xero has clearly communicated to me that the new integration is working as expected
Tim Rutter supported this idea · -
5 votes
An error occurred while saving the comment Tim Rutter commentedI suggest this aswell years ago, Xero silent removed the suggestion one day.
The Stripe payment method supports this.
And GoCardless API calls allow for query of fee amount before requesting payment so you can get an estimate.
Good luck
Tim Rutter supported this idea · -
4 votesTim Rutter supported this idea ·
-
2 votesTim Rutter supported this idea ·
-
5 votesTim Rutter supported this idea ·
-
6 votesTim Rutter supported this idea ·
-
6 votes
An error occurred while saving the comment Tim Rutter commentedMajor problem is the current GoCardless integration are not bank feed and are only holding account where the transactions and statement lines are only created by the integration
GoCardless needs full bank feed support like Stripe or Paypal or Tyro or eWay.
Tim Rutter supported this idea · -
2 votes
An error occurred while saving the comment Tim Rutter commentedMajor problem is the current GoCardless integration are not bank feed and are only holding account where the transactions and statement lines are only created by the integration
GoCardless needs full bank feed support like Stripe or Paypal or Tyro or eWay.
Tim Rutter supported this idea · -
15 votesTim Rutter shared this idea ·
-
24 votes
An error occurred while saving the comment Tim Rutter commentedThis is need
GoCardless has soo many problems
Tim Rutter supported this idea ·
Why has Xero merged the seperate topic of 'WebAuthn - passwordless, 1 step, 2FA' into this idea?
This idea is not the same, And Microsoft dev article does not even metion WebAuthn even thought its been a standard for 8 years.
For best authenticaion practises just go copy how Google does it!
Mainly choice of 2FA/MFA
- Passkey / WebAuthn < Xero does not support
- Hardware FIDO2 keys < Xero does not support
- OATH RFC6238 TOTP < Only one device supported
- In app prompt via push < Xero does not support
- SMS TOTP < Xero does not support
- Email TOTP < Xero does not support
- Backup OTP Codes < Xero does not support
Google supports any and all of these, any mix it the users (or Workspace admin perference).
Google allows multiple of the same type can be used, i.e. two OATH apps or multiple hardware FIDO2 keys. All very easily audited, each method can be separately removed and is tracked when it was used.
Whereas Xero currently only supports a single OATH device/app. :'(
Microsoft's short number match is very insecure, nobody else in the industry uses this method!
If you want Microsoft's short number match to be supported, it would be better for Xero to intergrate single-signon OAUTH with Microsoft, Google, and other auth providers.