Skip to content

feat: document SCA_SESSION_REQUIRED (409) and ACCOUNT_LOCKED (423) on quote authorize #761

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
+32 −3
Merged

feat: document SCA_SESSION_REQUIRED (409) and ACCOUNT_LOCKED (423) on quote authorize #761

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
10 changes: 9 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.

10 changes: 9 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.

2 changes: 2 additions & 0 deletions openapi/components/schemas/errors/Error409.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,7 @@ properties:
| EMAIL_OTP_EMAIL_ALREADY_EXISTS | Email address is already associated with an EMAIL_OTP credential |
| EMAIL_OTP_CREDENTIAL_SET_CHANGED | Tied EMAIL_OTP credential set changed after the signed-retry challenge was issued |
| PASSKEY_ALREADY_ENROLLED | The customer already has an enrolled passkey factor; only one passkey per customer is supported. Delete the existing one before enrolling another |
| SCA_SESSION_REQUIRED | The customer's Strong Customer Authentication login session is missing or expired. Re-authenticate the customer, then retry the request. Distinct from a `401`, which means the platform's own API credentials were rejected |
| CONFLICT | Generic resource-state conflict. Returned, for example, when `platformCustomerId` on a customer create call collides with an existing active customer on the same platform |
enum:
- TRANSACTION_NOT_PENDING_PLATFORM_APPROVAL
Expand All @@ -28,6 +29,7 @@ properties:
- EMAIL_OTP_EMAIL_ALREADY_EXISTS
- EMAIL_OTP_CREDENTIAL_SET_CHANGED
- PASSKEY_ALREADY_ENROLLED
- SCA_SESSION_REQUIRED
- CONFLICT
message:
type: string
Expand Down
13 changes: 12 additions & 1 deletion openapi/paths/quotes/quotes_{quoteId}_authorize.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,11 +64,22 @@ post:
'409':
description: >-
SCA is not required for this customer, or the quote has
no pending challenge to authorize.
no pending challenge to authorize. Also returned with
`SCA_SESSION_REQUIRED` when the customer's SCA login session is missing
or expired — re-authenticate the customer, then authorize again.
content:
application/json:
schema:
$ref: ../../components/schemas/errors/Error409.yaml
'423':
description: >-
Returned with `ACCOUNT_LOCKED` when the customer's login is temporarily
locked after too many failed authorization attempts. The customer must
wait for the lock to expire before authorizing again.
content:
application/json:
schema:
$ref: ../../components/schemas/errors/Error423.yaml
'429':
description: >-
Too many requests. Returned with `RATE_LIMITED` when authorization
Expand Down
Loading