Fix the Process Payment response specification to reflect the correct nested object structure.

[edgarmartinezlogos]

What changed?

This change adds the data property to the Process Payment response and nest the existing id, transaction_type, and status fields 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

{
	"id": "",
	"transaction_type": "",
	"status": ""
}

Now

{
	"data": {
		"id": "",
		"transaction_type": "",
		"status": ""
	}
}

Why?

The BigCommerce Payments API is already returning a response that conforms to the updated specifications defined in this PR.

[edgarmartinezlogos]

Hello @chris-nowicki ,
Hoping you’re the right person to ask—could you let me know the next step to get this PR merged? All checks have passed, but it looks like I don’t have permission to merge it (I don’t see the merge button).
Thanks in advance for your guidance.

[chris-nowicki]

Hello @chris-nowicki , Hoping you’re the right person to ask—could you let me know the next step to get this PR merged? All checks have passed, but it looks like I don’t have permission to merge it (I don’t see the merge button). Thanks in advance for your guidance.

merged ✅