Skip to main content
The partner initiates a credit limit increase on an existing card engagement with a single request. As the application moves through document collection, review, signing and the final decision, Nordiska emits webhook events that mirror those state changes. The partner collects supporting documents from the customer and uploads them via the API. Signing is hosted by Nordiska; the partner only needs to forward the customer to the signingUrl that arrives on the webhook.
Recommended reapplication cooldown: 90 days. Nordiska does not enforce this in code, but we recommend the partner prevents a customer from submitting a new credit limit increase application within 90 days of a previous decision, regardless of whether the previous application was approved or rejected.

Initiate Credit Limit Increase

Request body

Reason

reason is a tagged object discriminated by reasonType. Exactly one value must be provided. Example with OTHER:

EmploymentType

Response 200 OK

The application always starts in PROCESSING. Subsequent status changes are pushed via webhooks.

Upload Supporting Documents

When the CREDIT_LIMIT_INCREASE_DOCUMENTS_REQUIRED webhook fires, the customer must supply supporting documents (e.g. payslips or bank statements). The partner uploads them as multipart/form-data. Up to 5 files can be sent in a single request, and the endpoint can be called multiple times until all required documents have been provided.
Returns 200 OK on success.

Get Credit Limit Increase

Fetch the current state of a credit limit increase application.

Response 200 OK

additionalInformation is present whenever the status carries extra data. For most statuses it’s the same payload as the corresponding webhook; COMPLETED is the exception — approvedLimit is only available here, not on the webhook itself: approvedLimit has the same shape as appliedAmount and reflects the limit Nordiska approved, which may differ from what was applied for:

Credit Limit Increase Status

The application moves through the following statuses:

State diagram

Each transition is labelled with the webhook emitted when the application enters the target status. The initial PROCESSING status emits no webhook — observe it via Get Credit Limit Increase.

Webhook Events

One webhook is emitted per status change, except for the initial PROCESSING status, which emits none. Every payload carries creditLimitIncreaseId.

CREDIT_LIMIT_INCREASE_DOCUMENTS_REQUIRED

The customer needs to upload supporting documents (payslips for employed customers, bank statements supporting the claimed income).

CREDIT_LIMIT_INCREASE_DOCUMENT_REVIEW_STARTED

Documents have been received and are under review. No customer action required.

CREDIT_LIMIT_INCREASE_SIGNING_SESSION_CREATED

The customer must be redirected to signingUrl to sign the new credit agreement.

CREDIT_LIMIT_INCREASE_FINALIZING

The customer has signed and Nordiska is activating the new credit limit. No customer action required.

CREDIT_LIMIT_INCREASE_COMPLETED

The new credit limit is active on the engagement. Fetch Get Credit Limit Increase for the approvedLimit.

CREDIT_LIMIT_INCREASE_REJECTED

The application was rejected.
rejectReason is always CREDIT_LIMIT_INCREASE_REJECTED. The field is kept as an enum for forward compatibility.

CREDIT_LIMIT_INCREASE_FAILED

The application could not be processed due to an error rather than a credit decision.
failureCode is one of:

End-to-end sequence