Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for IBP(Instant Bank Pay) for Australia. #8

Open
iamdharmesh opened this issue Apr 22, 2024 · 2 comments
Open

Add Support for IBP(Instant Bank Pay) for Australia. #8

iamdharmesh opened this issue Apr 22, 2024 · 2 comments
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement.

Comments

@iamdharmesh
Copy link
Collaborator

iamdharmesh commented Apr 22, 2024

PR https://github.com/woocommerce/woocommerce-gateway-gocardless-private/pull/286 adds initial Instant Bank Pay support for the UK, DE, and FR. The goal for this issue is to add support for Australia as well.

Note: The pay_to scheme needs to be enabled on the merchant account to be able to use IBP in Australia.

@iamdharmesh iamdharmesh added priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement. labels Apr 22, 2024
@dkotter
Copy link
Collaborator

dkotter commented Apr 23, 2024

@dchambersgc Curious for your thoughts on this one. I had asked this question in last weeks meeting (or maybe the meeting before that) around adding the pay_to scheme to our GoCardless account so we could properly test Australia support. The response was something around this not being a priority at the moment so not something for us to worry about.

It would be fairly easy for us to add support for IBP in Australia if that is desired but ideally we would get that pay_to scheme added to our account so we could fully test this out (slight concern that without that scheme added, we can't test and risk releasing something that doesn't function correctly).

So I guess curious for your take on the priority for this piece? If we should just leave this in the backlog for now and come back to adding this support later or if this is something we want for our next release?

@dchambersgc
Copy link

If we should just leave this in the backlog for now and come back to adding this support later

Let's do this.

We can leave it as is, and future us can revisit it when we want to add the scheme to this integration

@diegocurbelo diegocurbelo transferred this issue from another repository Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: enhancement The issue is a request for an enhancement.
Projects
None yet
Development

No branches or pull requests

3 participants