fix: updating samples for schema changes

[pengying]

TL;DR

Updated API request examples for UMA payments to use the new source/destination structure instead of currency codes.

What changed?

• Updated the sandbox testing examples to use the new source and destination objects instead of sendingCurrencyCode and receivingCurrencyCode
• Updated the UMA payment examples to use the new structure with sourceType, destinationType, and umaAddress fields
• Changed senderUserInfo to senderCustomerInfo in the UMA payment example to reflect the correct parameter name
• Removed an unnecessary comment in the payouts quickstart example

How to test?

• Try executing the updated API requests against the sandbox environment
• Verify that UMA payments work correctly with the new request structure
• Confirm that sender information is properly passed using the senderCustomerInfo field

Why make this change?

The API has been updated to use a more structured approach for specifying payment sources and destinations, which provides better clarity and flexibility. This change ensures the documentation reflects the current API design and helps users implement UMA payments correctly.

[pengying]

• fix: updating samples for schema changes #194 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates API request examples across the documentation to use the new structured source and destination objects instead of the flat sendingCurrencyCode and receivingCurrencyCode fields. The changes include:

• Quote creation requests now use nested source and destination objects with explicit sourceType, destinationType, and related fields
• UMA payment examples corrected to use senderCustomerInfo instead of the incorrect senderUserInfo parameter name
• Documentation consistency improved by removing an unnecessary comment in the payouts quickstart

All changes are documentation-only updates that align the examples with the current API schema. The new structure provides better clarity and flexibility for specifying payment sources and destinations.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• This is a straightforward documentation-only PR that updates API examples to match the current schema. The changes are consistent across all files, properly structured, and align with the PR description. No code logic is affected.
• No files require special attention

Important Files Changed

Filename	Overview
mintlify/global-p2p/platform-tools/sandbox-testing.mdx	Updated quote creation examples to use new source/destination structure instead of flat currency codes
mintlify/payouts-and-b2b/quickstart.mdx	Removed unnecessary comment from quote creation example
mintlify/snippets/sending/uma.mdx	Updated UMA payment examples to use new source/destination structure and corrected parameter name from senderUserInfo to senderCustomerInfo

_{Last reviewed commit: 6edf2ee}