feat: adding external account verification to UPI accounts

[pengying]

TL;DR

Updated Stainless configuration for Lightspark Grid SDK, fixing type conflicts and adding beneficiary name verification status.

What changed?

• Renamed organization from "grid" to "Lightspark Grid"
• Updated package names and production repositories for TypeScript and Kotlin SDKs
• Simplified schema handling by removing redundant model references
• Fixed type conflicts by removing discriminator properties from base schemas
• Added beneficiaryNameVerificationStatus field to UPI account external account info
• Updated Exchange Rates description to be more concise
• Adjusted example requests to use /quotes endpoint instead of /config

[pengying]

• feat: adding external account verification to UPI accounts #169 👈 (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 message.

feat: adding external account verification to UPI accounts

Edit this comment to update it. It will appear in the SDK's changelogs.

✅ grid-typescript studio · code · diff

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

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

✅ grid-openapi studio · code · diff

Your SDK built successfully.
generate ✅

✅ grid-kotlin studio · code · diff

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-10 02:49:25 UTC

[greptile-apps]

Greptile Overview

Greptile Summary

This PR updates the Stainless SDK generation configuration (organization name, TS/Kotlin package metadata, production repo targets) and adjusts how schema unions/discriminators are handled by removing discriminator properties from several base schemas to avoid allOf type conflicts in generated SDKs.

It also updates the OpenAPI specs (root + mintlify + split spec) by:

• simplifying the Exchange Rates tag description, and
• adding beneficiaryNameVerificationStatus (MATCHED / PARTI_MATCHED / NO_MATCH) to UpiAccountExternalAccountInfo.

These changes affect both the published API docs (mintlify) and the SDK generation pipeline (Stainless), so correctness of the schema transforms and generated README example requests is important.

Confidence Score: 4/5

• Mostly safe to merge, but fix the SDK README example request and a small formatting issue first.
• Schema and doc changes are straightforward, and the new UPI verification status field is consistently added across specs. The main merge blocker is the Stainless README example switching to POST /quotes while still using empty params, which will generate broken snippets; also one schema file is missing a trailing newline.
• .stainless/stainless.yml; openapi/components/schemas/external_accounts/UpiAccountExternalAccountInfo.yaml

Important Files Changed

Filename	Overview
.stainless/stainless.yml	Updates org/package/repo settings and adds OpenAPI transformations that strip discriminator fields and remove empty base allOf refs.
mintlify/openapi.yaml	Updates Exchange Rates tag description and adds beneficiaryNameVerificationStatus to UpiAccountExternalAccountInfo schema.
openapi.yaml	Mirrors mintlify OpenAPI changes: shortens Exchange Rates tag description and adds beneficiaryNameVerificationStatus to UpiAccountExternalAccountInfo.
openapi/components/schemas/external_accounts/UpiAccountExternalAccountInfo.yaml	Adds beneficiaryNameVerificationStatus enum field to UPI external account info; file currently lacks trailing newline.
openapi/openapi.yaml	Shortens Exchange Rates tag description in the split OpenAPI spec.

Sequence Diagram

sequenceDiagram
  participant Dev as Developer
  participant Stainless as Stainless (config + transforms)
  participant Spec as OpenAPI (openapi.yaml)
  participant SDK as Generated SDKs (TS/Kotlin)

  Dev->>Stainless: Update .stainless/stainless.yml (org/package/repos)
  Dev->>Spec: Add beneficiaryNameVerificationStatus to UPI external account info
  Stainless->>Spec: Apply transformations (remove discriminator $refs, remove allOf base $refs)
  Stainless->>SDK: Generate SDKs + README snippets
  SDK-->>Dev: SDK types compile (type conflicts reduced)
  SDK-->>Dev: README snippets depend on example request validity

Loading

[greptile-apps]

_{5 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (2)

openapi/components/schemas/external_accounts/UpiAccountExternalAccountInfo.yaml
Missing trailing newline

This file ends without a final newline (shows up as \ No newline at end of file in the diff). Some tooling (formatters/linters, schema bundlers, and CI diffs) treats this as a formatting error; please add a trailing newline to avoid noisy diffs/failures.

_{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: openapi/components/schemas/external_accounts/UpiAccountExternalAccountInfo.yaml
Line: 1:3

Comment:
**Missing trailing newline**

This file ends without a final newline (shows up as `\ No newline at end of file` in the diff). Some tooling (formatters/linters, schema bundlers, and CI diffs) treats this as a formatting error; please add a trailing newline to avoid noisy diffs/failures.

<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.

---

.stainless/stainless.yml
Invalid README example call

.stainless/stainless.yml switches the README default/headline snippets to post /quotes but leaves params: {}. In the spec, POST /quotes requires a request body (it’s not an empty request), so this example request will generate SDK README snippets that don’t compile/run against the generated client. Update the example to include the required body fields (or point the snippet back at an endpoint that supports an empty request).

Prompt To Fix With AI

This is a comment left during a code review.
Path: .stainless/stainless.yml
Line: 287:290

Comment:
**Invalid README example call**

`.stainless/stainless.yml` switches the README `default`/`headline` snippets to `post /quotes` but leaves `params: {}`. In the spec, `POST /quotes` requires a request body (it’s not an empty request), so this example request will generate SDK README snippets that don’t compile/run against the generated client. Update the example to include the required body fields (or point the snippet back at an endpoint that supports an empty request).

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