Docs: add SWIFT payout documentation to external-account examples#662
Merged
Conversation
… tab Per shreya's feedback the separate guide page was excessive. Search discoverability is preserved: snippet tab titles are indexed per importing page, so the SWIFT (International) tab surfaces on all four External Accounts pages. Co-Authored-By: shreyav <shreyav@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Contributor
|
@greptileai review |
pengying
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
Documents SWIFT payouts, which were previously absent from the narrative docs (only visible in the generated API-reference schema). Requested by shreya after a customer couldn't find how to do SWIFT payouts — and searching "SWIFT" in the docs turned up nothing.
SWIFT_ACCOUNTexternal account (the payout itself is the standard quote → execute flow).A dedicated "SWIFT Payouts" guide page was initially included but removed per shreya's feedback (excessive). Search still works without it: Mintlify indexes snippet tab titles per importing page — verified on production, where searching "PIX" surfaces the "Brazil" tab entries on all four External Accounts pages; "SWIFT (International)" will index the same way after deploy.
API mechanics verified against the OpenAPI spec and sparkcore: SWIFT is opted into via the account type (no request-level
paymentRailparam);SwiftAccountInfoBaserequiresswiftCode,bankName,country, andaccountNumberoriban; SWIFT accounts are multi-currency (currency= what the destination account holds, may differ fromcountry).Deliberately out of scope (needs product input): which corridors are SWIFT-enabled, fees, and settlement times.
Test plan
python3 -m json.tool mintlify/docs.json— valid JSONmint broken-links— no broken links introduced (24 pre-existing failures in untouched global-accounts snippets)SwiftAccountInfoBaseschema with a consistent Nigerian bank/BIC (Codex P2 fix)openapi/edits, so no rebundle neededPrivate
Plan (S3, internal only)
Public
Adds SWIFT payout documentation to the external-accounts examples across all use-case sections.
Slack thread: https://lightsparkgroup.slack.com/archives/D0AH5T8FMGE/p1783379896777279
🤖 volatile-nonce-2(#2) | Feedback
Original PR: #655