Skip to content

Conversation

@JasonCWang
Copy link
Contributor

No description provided.

Copy link
Contributor Author

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

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 12, 2026

Greptile Overview

Greptile Summary

Added documentation for purpose of payment field in cross-currency quote requests. The accordion includes correct field name (senderCustomerInfo) and accurate purpose of payment codes matching the OpenAPI schema.

Confidence Score: 4/5

  • This documentation-only PR is safe to merge with minor clarification needed
  • The documentation accurately reflects the API schema with correct field names and enum values. The accordion follows Mintlify best practices. Minor issue: the description says "external account or UMA destinations" but the OpenAPI schema indicates senderCustomerInfo is "Only relevant for UMA destinations" - this inconsistency was already flagged in previous review threads.
  • No files require special attention

Important Files Changed

Filename Overview
mintlify/snippets/sending/cross-currency.mdx Added accordion documenting purpose of payment field with correct codes and field name

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 file reviewed, 2 comments

Edit Code Review Agent Settings | Greptile

Comment on lines 61 to 63
"senderInfo": {
"purposeOfPayment": "GOODS_OR_SERVICES"
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

incorrect field name - should be senderCustomerInfo not senderInfo

per openapi/components/schemas/quotes/QuoteRequest.yaml:47-66, the quote request uses senderCustomerInfo

Suggested change
"senderInfo": {
"purposeOfPayment": "GOODS_OR_SERVICES"
}
"senderCustomerInfo": {
"PURPOSE_OF_PAYMENT": "GOODS_OR_SERVICES"
}
Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/sending/cross-currency.mdx
Line: 61:63

Comment:
incorrect field name - should be `senderCustomerInfo` not `senderInfo`

per openapi/components/schemas/quotes/QuoteRequest.yaml:47-66, the quote request uses `senderCustomerInfo`

```suggestion
    "senderCustomerInfo": {
      "PURPOSE_OF_PAYMENT": "GOODS_OR_SERVICES"
    }
```

How can I resolve this? If you propose a fix, please make it concise.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oo i think this one is right

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shuttt my b

Comment on lines 52 to 53
<Accordion title="Including purpose of payment">
Some payment corridors require a purpose of payment. Include it in the `senderInfo` object:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add context about when this field is applicable

per the OpenAPI schema (openapi/components/schemas/quotes/QuoteRequest.yaml:47-51), senderCustomerInfo is "Only relevant for UMA destinations." this accordion doesn't clarify when purpose of payment is needed, which could confuse users trying to send to non-UMA destinations

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix With AI
This is a comment left during a code review.
Path: mintlify/snippets/sending/cross-currency.mdx
Line: 52:53

Comment:
add context about when this field is applicable

per the OpenAPI schema (openapi/components/schemas/quotes/QuoteRequest.yaml:47-51), `senderCustomerInfo` is "Only relevant for UMA destinations." this accordion doesn't clarify when purpose of payment is needed, which could confuse users trying to send to non-UMA destinations

<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>

How can I resolve this? If you propose a fix, please make it concise.

@JasonCWang JasonCWang force-pushed the 02-11-add_optional_purpose_of_payment_example_to_cross_currency branch from 00339f7 to 9b19c48 Compare February 12, 2026 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants