feat(payment): PAYMENTS-11577 Render fields coming from provider init… - #3014
Draft
bc-alfreid wants to merge 2 commits into
Draft
feat(payment): PAYMENTS-11577 Render fields coming from provider init…#3014bc-alfreid wants to merge 2 commits into
bc-alfreid wants to merge 2 commits into
Conversation
bc-alfreid
force-pushed
the
PAYMENTS-11577
branch
from
May 15, 2026 03:11
9171160 to
620ce96
Compare
…ialzation data - usage of purchase order
bc-alfreid
force-pushed
the
PAYMENTS-11577
branch
3 times, most recently
from
May 15, 2026 04:41
4b8b729 to
908c218
Compare
…nt for future use
bc-alfreid
force-pushed
the
PAYMENTS-11577
branch
from
May 15, 2026 05:00
0ebb44a to
cd97521
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…ialzation data - usage of purchase order
What/Why?
For purchase order payment method, we want to be able to render purchase order number field, while not needing to create strategy specific to purchase order, and keep the changes within offline payment.
This is done by using formFieldsData as part of initializationData of purchaseorder provider
Rollout/Rollback
Revert
Testing
TBD