-
Notifications
You must be signed in to change notification settings - Fork 69
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
Update handling for PR as a country for terminal locations #10349
Update handling for PR as a country for terminal locations #10349
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
Size Change: 0 B Total Size: 1.29 MB ℹ️ View Unchanged
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code-only review: The change matches what Stripe expects. Thanks for slipping this in so quickly, @deepakpathania 🎉
Review checklist
Parameter | Result |
---|---|
Approach | ✅ All good |
Implementation | ✅ All good |
Automated tests | ✅ All good |
Naming | ✅ All good |
Typing | ✅ All good |
Code comments | ✅ All good |
Changelog | ✅ All good |
Documentation | Not applicable |
PR description | ✅ All good |
Testing instructions | We could expand it a little to inform how to test the API. |
Manual testing |
tests/unit/admin/test-class-wc-rest-payments-terminal-locations-controller.php
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, forgot to approve earlier.
…into update/terminal-controller-PR-country-handling
Thanks for this @deepakpathania, I don't see any difference in the response we get from the locations endpoint. To avoid creating a new store and onboarding via Puerto Rico I've tested this PR using the Jetpack Beta option, activating the
GET /wc/v3/wc_stripe/terminal/locations/store 200 ok
GET /wc/v3/wc_stripe/connection_tokens 200 ok
Which causes a 400 when we POST to
|
Actually I see now the endpoint having I'm trying to create a jurassic ninja PR-based store following the setup here PdfdoF-D-p2 but despite following all the instructions, is restricted (Update WooPayments business details) and payments are disabled until I provide a Social Security Number, so I cannot test those with the reader. Could you provide credentials to a Puerto Rico-based store with functional WooCommerce Payments for testing? |
I think you could reach out to @malinajirka to assist with getting this setup. Or let me check if someone from the team can assist here. |
Thanks! I've tried a couple times and finally passed verification on a subsequent try. It seems we have a winner! It works 🎉 v1/terminal/locations/tml_F6lNlgv4nEj032
|
Fixes #10353
Changes proposed in this Pull Request
PR
as a state andUS
as the country in casePR
is set as the country for the terminal locations endpoint.Testing instructions
PR
as state andUS
as country in casePR
is the location.npm run changelog
to add a changelog file, choosepatch
to leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge