feat: adding purpose of payment to quote

[pengying]

Adding purpose of payment to quotes

[pengying]

• feat: adding purpose of payment to quote #214 👈 (View in Graphite)
• main

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

[github-actions]

✱ Stainless preview builds

This PR will update the grid SDKs with the following commit messages.

kotlin

feat(api): add purposeOfPayment parameter to quote create

openapi

feat(api): add purposeOfPayment field to QuoteRequest

python

feat(api): add purpose_of_payment parameter to quotes create method

typescript

feat(api): add purposeOfPayment parameter to quotes create

✅ grid-openapi studio · code

Your SDK built successfully.
generate ✅

✅ grid-typescript studio · code

Your SDK built successfully.
generate ✅ → build ✅ → lint ✅ → test ✅

npm install https://pkg.stainless.com/s/grid-typescript/276ab08f050996fa228bca5fa61967cd173f099e/dist.tar.gz

✅ grid-python studio · code

Your SDK built successfully.
generate ✅ → build ✅ → lint ✅ → test ✅

pip install https://pkg.stainless.com/s/grid-python/4f09da11f22417f2afffd8896d9765d755aa7f04/grid-0.0.1-py3-none-any.whl

✅ grid-kotlin studio · code

Your SDK built successfully.
generate ✅ → build ✅ → lint ✅ → test ✅

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-02-20 02:26:33 UTC

[greptile-apps]

Greptile Summary

Adds purposeOfPayment field to quote requests, moving it from senderCustomerInfo.PURPOSE_OF_PAYMENT to a top-level field with a dedicated enum schema.

• Created new PurposeOfPayment schema with 12 enum values (GIFT, SELF, GOODS_OR_SERVICES, etc.)
• Added optional purposeOfPayment field to QuoteRequest schema
• Updated documentation to show new field usage instead of senderCustomerInfo pattern
• Both bundled OpenAPI specs (openapi.yaml and mintlify/openapi.yaml) regenerated

Issues found:

• CLI not updated: cli/src/commands/quotes.ts:180 still uses old senderCustomerInfo.PURPOSE_OF_PAYMENT pattern
• Enum inconsistency: New PurposeOfPayment enum differs from existing NgnAccountExternalAccountInfo.purposeOfPayment (different order, additional TRAVEL/OTHER values)

Confidence Score: 3/5

• Safe to merge with follow-up work needed for CLI update and enum consistency
• The OpenAPI schema changes are well-structured and documentation is properly updated. However, the CLI still uses the old pattern and there's an inconsistency with existing purposeOfPayment enums that should be addressed
• Review cli/src/commands/quotes.ts for CLI update and openapi/components/schemas/external_accounts/NgnAccountExternalAccountInfo.yaml for enum consistency

Important Files Changed

Filename	Overview
openapi/components/schemas/quotes/PurposeOfPayment.yaml	New schema defining purpose of payment enum with 12 values for quote requests
openapi/components/schemas/quotes/QuoteRequest.yaml	Added purposeOfPayment field to quote request schema, creating potential dual paths with senderCustomerInfo
mintlify/snippets/sending/cross-currency.mdx	Updated documentation to use new purposeOfPayment field instead of senderCustomerInfo.PURPOSE_OF_PAYMENT

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Client creates quote request] --> B{Payment corridor requires<br/>purpose of payment?}
    B -->|Yes<br/>e.g., India| C[Include purposeOfPayment field<br/>GIFT, SELF, GOODS_OR_SERVICES, etc.]
    B -->|No| D[Optional: Include purposeOfPayment]
    C --> E[POST /quotes]
    D --> E
    E --> F[Quote created with locked rate]
    F --> G[Execute quote]
    G --> H[Payment processed]

Loading

_{Last reviewed commit: 93ac62f}

[greptile-apps]

_{5 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Inconsistent with existing purposeOfPayment enum in NgnAccountExternalAccountInfo.yaml. The NGN schema has different order (LOAN_PAYMENT before TAX_PAYMENT) and is missing TRAVEL and OTHER values. Consider unifying these enums or using a $ref to share the same definition.

Prompt To Fix With AI

This is a comment left during a code review.
Path: openapi/components/schemas/quotes/PurposeOfPayment.yaml
Line: 5-17

Comment:
Inconsistent with existing `purposeOfPayment` enum in `NgnAccountExternalAccountInfo.yaml`. The NGN schema has different order (`LOAN_PAYMENT` before `TAX_PAYMENT`) and is missing `TRAVEL` and `OTHER` values. Consider unifying these enums or using a `$ref` to share the same definition.

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

[greptile-apps]

The CLI (cli/src/commands/quotes.ts:180) still uses the old pattern senderCustomerInfo.PURPOSE_OF_PAYMENT instead of this new top-level purposeOfPayment field. Update the CLI to use the new field.

Prompt To Fix With AI

This is a comment left during a code review.
Path: openapi/components/schemas/quotes/QuoteRequest.yaml
Line: 47-48

Comment:
The CLI (`cli/src/commands/quotes.ts:180`) still uses the old pattern `senderCustomerInfo.PURPOSE_OF_PAYMENT` instead of this new top-level `purposeOfPayment` field. Update the CLI to use the new field.

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