From 8e4584707e67d66986dd43c6e0a2ea461ea783c8 Mon Sep 17 00:00:00 2001 From: Jeremy Date: Wed, 29 Jul 2026 06:04:22 +0000 Subject: [PATCH] Add SCA_NOT_COMPLETED outgoing transaction failure reason --- mintlify/openapi.yaml | 6 +++++- openapi.yaml | 6 +++++- .../transactions/OutgoingTransactionFailureReason.yaml | 8 ++++++++ 3 files changed, 18 insertions(+), 2 deletions(-) diff --git a/mintlify/openapi.yaml b/mintlify/openapi.yaml index 0ae3a6da0..0744dc17f 100644 --- a/mintlify/openapi.yaml +++ b/mintlify/openapi.yaml @@ -20373,7 +20373,11 @@ components: - LIGHTNING_PAYMENT_FAILED - FUNDING_AMOUNT_MISMATCH - COUNTERPARTY_POST_TX_FAILED - 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 + 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. RailSelectionMode: type: string enum: diff --git a/openapi.yaml b/openapi.yaml index 0ae3a6da0..0744dc17f 100644 --- a/openapi.yaml +++ b/openapi.yaml @@ -20373,7 +20373,11 @@ components: - LIGHTNING_PAYMENT_FAILED - FUNDING_AMOUNT_MISMATCH - COUNTERPARTY_POST_TX_FAILED - 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 + 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. RailSelectionMode: type: string enum: diff --git a/openapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml b/openapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml index 8af526f7a..422531614 100644 --- a/openapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml +++ b/openapi/components/schemas/transactions/OutgoingTransactionFailureReason.yaml @@ -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.