Skip to content

Add SCA_NOT_COMPLETED outgoing transaction failure reason #762

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jklein24 merged 1 commit into from
Jul 30, 2026
+18 −2
Merged

Add SCA_NOT_COMPLETED outgoing transaction failure reason #762

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion mintlify/openapi.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 5 additions & 1 deletion openapi.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 8 additions & 0 deletions openapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,15 @@ enum:
- LIGHTNING_PAYMENT_FAILED
- FUNDING_AMOUNT_MISMATCH
- COUNTERPARTY_POST_TX_FAILED
- SCA_NOT_COMPLETED
description: >-
Reason for failure of an outgoing transaction. This is used to provide more
context on why a transaction failed. If the transaction is not in a failed
state, this field is omitted.


`SCA_NOT_COMPLETED` means the customer did not satisfy the Strong Customer
Authentication challenge before it expired, so the transaction was never
authorized and no funds were moved. Only occurs for customers in a region
where SCA is required (e.g. the EU). Create a new quote to try again, and have
the customer authorize it while the challenge is live.
Loading