- Issue created by @c_archer
- 🇬🇧United Kingdom mwjansen Bristol
All are required by Opayo at different stages:
We need 'Cardholder Name' (not divided into first name and second name) for card tokenisation.
Then later, the API for submitting a transaction requires separate 'First Name' and 'Last Name' fields.The 'Drop in form method' will still ask for the separate first name and last name (in addition to the cardholder name), they are just part of the 'Address'
I've experimented with just displaying 'first name' and 'last name' but decided against.
- 🇬🇧United Kingdom c_archer Cumbria
Can this info not be grabbed from the profile and skip these fields all together
- 🇬🇧United Kingdom mwjansen Bristol
If it's a guest user I don't think we can rely on there being a profile available and we would still need the cardholder's 'First Name' and 'Last Name' fields. The only tweak possible, in that case, would be to remove the 'Cardholder Name' field and create it on-the fly, where needed, from the 'First Name' and 'Last Name'. I could add an option to the config to make it behave that way.
For a logged in user, yes, a possible behaviour is that it assumes the profile first and last name is the cardholder. Again, I could add a toggle to make it behave that way.
In both cases I would keep the current behaviour as the default, because I think it's the 'safest' way of doing it - i.e. without baking in certain assumptions about the cardholder.
- 🇬🇧United Kingdom c_archer Cumbria
If the user is a guest, we can still grab from their profile as they will enter this either as shipping or billing profile and then we send that to sage reducing the need to enter it twice or three times in the current case.