Skip to content

[FR] Allow full access to drop-in customization options #60

@jmauzyk

Description

@jmauzyk

We've been experiencing an issue in which customers were having difficulty checking out with no apparent cause. After reviewing several session replays, we found a common thread between them. It appears that the users were using autofill (from the browser or a password manger) to enter their credit card details, but without their CVV. Because the default drop-in UI configuration includes placeholder text for each field, users see the “•••” placeholder text in the CVV field and mistake it for actual input. As a result, it appears to users that they're being prevented from completing payment for no reason.

It would be helpful if this plugin allowed full control of all the drop-in UI configuration options, especially those relevant to field overrides. This would allow us full control of how we would like to present payment options to customers, and would make this plugin that much more powerful.

Additionally, it would also be beneficial if these options could be configured in the plugin config file, similar to how Verbb handles Formie theme configuration. This would allow these options to be configured outside of front-end templates, resulting in cleaner code.

Thanks for your consideration! I'd be happy to contribute a PR if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions