Fix the Process Payment response specification to reflect the correct nested object structure. #1215
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.
What changed?
This change adds the
dataproperty to the Process Payment response and nest the existingid,transaction_type, andstatusfields within it, consistent with other response objects in the V3 API (Example: Create Access Token https://github.com/bigcommerce/docs/blob/main/reference/payments/access-tokens_payments.v3.yml#L105)Before
Now
Why?
The BigCommerce Payments API is already returning a response that conforms to the updated specifications defined in this PR.
