Add high-limit payment rails to PaymentRail enum

[mohamedwane]

Summary

Adds 8 new payment rail enum values to components.schemas.PaymentRail, keeping the existing alphabetical ordering and formatting:

• ACH_COLOMBIA
• BRE_B
• CIPS
• INSTAPAY
• NEFT
• PESONET
• RTGS
• UNIONPAY

The source enum (openapi/components/schemas/common/PaymentRail.yaml) was edited and the spec rebundled via make build, regenerating openapi.yaml and mintlify/openapi.yaml so the repo stays internally consistent. No other changes — the payment_rail field on AccountDestination already references this shared enum, so it picks up the new values automatically.

Why

This keeps the spec in parity with lightsparkdev/webdev#28108 ("[M0.6] support explicit rail selection in Grid quote endpoint"), which hand-added these 8 PaymentRail values to webdev's vendored mirror of this spec.

⚠️ Merge-order requirement

This must merge before (or in lockstep with) webdev#28108. webdev re-syncs its vendored copy from this repo (via grid-api/update_schema.sh, which clones this repo as the source of truth). If webdev re-syncs before these values land upstream, the next sync would silently drop the hand-added rails and break webdev's typecheck.

https://claude.ai/code/session_01KtztB3MumSMo7V4qZpioew

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
grid-flow-builder	Ignored		Jun 15, 2026 9:36pm

[github-actions]

✱ Stainless preview builds for grid

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

cli

chore(internal): regenerate SDK with no functional changes

csharp

feat(api): add payment rail enum values to transfer out operations

go

feat(api): add payment rail enum values to transfer out destination

kotlin

feat(api): add payment rails to TransferOutRequest

openapi

feat(api): add 8 values to payment rail enum

php

feat(api): add payment rail options to PaymentRail enum

python

feat(api): add payment rail types to transfer_out destination parameters

ruby

feat(api): add 8 payment rail options to transfer out request

typescript

feat(api): add payment rail enum values to transfer-out operations

✅ grid-openapi studio · code

Your SDK build had at least one "note" diagnostic.
generate ✅

✅ grid-ruby studio · code

Your SDK build had at least one "note" diagnostic.
generate ✅ → build ✅ → lint ✅ → test ✅

⚠️ grid-go studio · code

Your SDK build had a failure in the lint CI job, which is a regression from the base state.
generate ✅ → build ✅ → lint ❗ → test ❗

go get github.com/stainless-sdks/grid-go@b7a676b130fc8975e5d5da0a8007d47ef59479ea

✅ grid-kotlin studio · code

Your SDK build had at least one "note" diagnostic.
generate ✅ → build ✅ → lint ✅ → test ✅

✅ grid-typescript studio · code

Your SDK build had at least one "note" diagnostic.
generate ✅ → build ✅ → lint ✅ → test ✅

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

⚠️ grid-python studio · code

Your SDK build had a failure in the lint CI job, which is a regression from the base state.
generate ✅ → build ✅ → lint ❗ → test ❗

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

⚠️ grid-csharp studio · code

Your SDK build had a failure in the build CI job, which is a regression from the base state.
generate ⚠️ → build ❗ → lint ✅ → test ❗

✅ grid-php studio · code

Your SDK build had at least one "note" diagnostic.
generate ✅ → lint ✅ → test ✅

⚠️ grid-cli studio · code

Your SDK build had a failure in the test CI job, which is a regression from the base state.
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-06-15 22:01:32 UTC

[greptile-apps]

Greptile Summary

This PR extends the PaymentRail enum with 8 new high-limit payment rail values, syncing the grid-api spec with the hand-added values in lightsparkdev/webdev#28108. All three files (openapi/components/schemas/common/PaymentRail.yaml, openapi.yaml, mintlify/openapi.yaml) are updated consistently, with the source YAML edited and the bundled files regenerated via make build as required.

• Adds ACH_COLOMBIA, BRE_B, CIPS, INSTAPAY, NEFT, PESONET, RTGS, and UNIONPAY to the enum, all correctly inserted in alphabetical order.
• No structural or logic changes — this is a pure additive spec extension that downstream consumers of the payment_rail field pick up automatically.

Confidence Score: 5/5

Safe to merge — purely additive enum extension with all three files in sync and correct alphabetical ordering throughout.

The change adds 8 new enum values to the source YAML and the two generated bundles are consistent with each other and the source. The edit follows the repo's prescribed workflow (edit source, run make build), alphabetical ordering is preserved, and no existing values were touched. There is no logic, no migration, and no breaking change — existing clients that don't recognize the new values simply won't send them.

No files require special attention.

Important Files Changed

Filename	Overview
openapi/components/schemas/common/PaymentRail.yaml	Source enum definition — 8 new values added in correct alphabetical order, description unchanged.
openapi.yaml	Generated bundle — identical enum additions, consistent with source; correctly regenerated via make build.
mintlify/openapi.yaml	Mintlify-targeted generated bundle — identical enum additions, consistent with source and root bundle.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["openapi/components/schemas/common/PaymentRail.yaml\n(source — edited here)"] -->|make build| B["openapi.yaml\n(generated bundle)"]
    A -->|make build| C["mintlify/openapi.yaml\n(generated bundle)"]

    subgraph "New enum values added"
        N1["ACH_COLOMBIA"]
        N2["BRE_B"]
        N3["CIPS"]
        N4["INSTAPAY"]
        N5["NEFT"]
        N6["PESONET"]
        N7["RTGS"]
        N8["UNIONPAY"]
    end

    A -.->|contains| N1
    A -.->|contains| N2
    A -.->|contains| N3
    A -.->|contains| N4
    A -.->|contains| N5
    A -.->|contains| N6
    A -.->|contains| N7
    A -.->|contains| N8

Loading

_{Reviews (1): Last reviewed commit: "Add high-limit payment rails to PaymentR..." | Re-trigger Greptile}