Add SCA_NOT_COMPLETED outgoing transaction failure reason

[jklein24]

Summary

Adds SCA_NOT_COMPLETED to OutgoingTransactionFailureReason.

When a customer in an SCA-regulated region (e.g. the EU) is issued a Strong Customer Authentication challenge for a money movement and never satisfies it, the challenge expires and the transaction fails. Today that surfaces with no failureReason at all, so integrators can't tell an abandoned authorization apart from a genuine payment failure — the two need completely different follow-up.

The new value is scoped narrowly to the case where nothing moved, so the guidance in the description ("no funds were moved; create a new quote and have the customer authorize it while the challenge is live") is always true when a client sees it. Failures where an intermediate leg already executed and needs operator reconciliation continue to surface as QUOTE_EXECUTION_FAILED, matching how other operational failures are reported.

Compatibility

Non-breaking. oasdiff breaking against main reports 0 errors, 17 warnings — all the same response-property-enum-value-added informational warning, one per operation that returns an outgoing transaction. The repo's breaking-changes gate runs with --fail-on ERR, so this passes, and info.version is unchanged per the repo convention of bumping only for breaking changes.

Test plan

• make build — rebundled openapi.yaml + mintlify/openapi.yaml; the diff is limited to this enum and its description
• make lint-openapi — "Woohoo! Your API description is valid. 🎉", 0 errors (remaining warnings are pre-existing repo-wide schema-properties-have-examples noise, untouched by this change)
• oasdiff breaking main HEAD --fail-on ERR — exit 0

Requested by @jklein24

Original PR: #760

[akanter]

• Add SCA_NOT_COMPLETED outgoing transaction failure reason #762 👈 (View in Graphite)
• main

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

[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

go

feat(api): add SCA_NOT_COMPLETED to OutgoingTransactionFailureReason enum

kotlin

feat(api): add SCA_NOT_COMPLETED failure reason to OutgoingTransaction

openapi

feat(api): add SCA_NOT_COMPLETED to transaction failure reason enum

php

feat(api): add SCA_NOT_COMPLETED to OutgoingTransaction FailureReason enum

python

feat(api): add SCA_NOT_COMPLETED to OutgoingTransaction failure_reason enum

ruby

feat(api): add SCA_NOT_COMPLETED failure reason to OutgoingTransaction

typescript

feat(api): add SCA_NOT_COMPLETED failure reason to OutgoingTransaction

⚠️ grid-openapi studio · code

Your SDK build had at least one "warning" 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@3e59b984666648a88616990d2ab965d3dd7757b4

⚠️ grid-kotlin 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 ❗

⚠️ 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/8a535cc5d82e4c63e83355e8f8bbb18023b6c7d4/grid-0.0.1-py3-none-any.whl

✅ grid-typescript studio · conflict

Your SDK build had at least one note diagnostic.

✅ 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-07-30 01:25:00 UTC

[greptile-apps]

Greptile Summary

      ⚡☠️  S C A   D O O M  ☠️⚡
     /|  _.-' METAL AUTHORIZATION '-._  |\
    /_|_/_______________________________\|_\
       \m/  LET THE EXPIRED CHALLENGE FALL  \m/

NO FUNDS MOVED — FORGE A NEW QUOTE AND AUTHORIZE AGAIN.

• Adds SCA_NOT_COMPLETED to the outgoing transaction failure-reason enum.
• Documents that this reason represents an expired, unsatisfied SCA challenge where no funds moved.
• Regenerates the root and Mintlify OpenAPI bundles with the updated contract.

Confidence Score: 5/5

The PR appears safe to merge, with the source schema and both generated OpenAPI bundles updated consistently.

The additive enum value is narrowly documented, requires no breaking-version bump under repository conventions, and introduces no concrete in-repository contract, build, or synchronization failure.

Important Files Changed

Filename	Overview
openapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml	Adds and documents the new outgoing transaction failure reason in the canonical modular schema.
openapi.yaml	Correctly reflects the enum and description changes in the generated root bundle.
mintlify/openapi.yaml	Remains synchronized with the root generated bundle for local Mintlify API-reference rendering.

_{Reviews (1): Last reviewed commit: "Add SCA_NOT_COMPLETED outgoing transacti..." | Re-trigger Greptile}