Collections and legal follow-up
Follow up arrears — delinquency state, collection detail and the legal process behind an unpaid balance.
createFollowUpByMainCustomerNumber
Creates a follow-up for a corporate customer using MainCustomerNumber. Validates customer exists and is corporate. Cancels active main cards (excluding supplementary and already bank-cancelled cards) by calling ChangeCardStatus on each. Finally, creates follow-up queue entry using MainCustomerNumber and Channel.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
createFollowUpByMainCustomerNumber › Request Body
channelThree-digit code identifying the channel on behalf of which the request is made (e.g. 002 for Internet). Mandatory in every request. Used for entitlement checks, limit enforcement and audit logging. Channel codes are managed through configuration parameters and may change over time. Refer to the Channels page for the current list of valid codes.
mainCustomerNumberMain customer number whose credit cards are closed and which is queued for legal follow-up. The null check cannot fail on this non-nullable integer, so 0 passes it and fails the customer lookup instead.
createFollowUpByMainCustomerNumber › Responses
Success.
The operation returns no body. It runs in three stages: it closes the customer's credit cards, then writes one legal follow-up queue row.
Only rows of the credit card master carrying this main customer number are considered, so debit cards are never touched. Of those, supplementary cards, cards that are not the current card of their reference, and cards already bank-cancelled with reason KT are skipped. Each remaining card is set to the bank-cancel status with reason KT, with reissue off and the closing date set to the server clock; the request cannot choose the status, the reason or the date.
A customer that holds card records but none that qualify is not an error: no card changes and the queue row is still written, so a 200 does not mean a card was closed. The cards are changed one at a time and the first refusal aborts the operation, after which the queue row is not written.
The queue row is written with status N, valid flag 1, follow-up date today, the inserting user taken from the calling identity, and — because this operation never sends them — business key 0 and follow-up reason 3. Use Add To Legal Follow Up to set a different reason.
addToLegalFollowUp
Adds a customer account to the legal follow-up queue, including business key and follow-up reason. Ensures validation of input parameters before invoking the legal management service.
Headers
evrst-ptrnidCorrelation id for this request. Echo it in your own logs to trace the call through the platform.
addToLegalFollowUp › Request Body
MainCustomerNumberMain customer number to place in legal follow-up. Must not be zero.
FollowupReasonReason for placing the customer in legal follow-up. Sent downstream unchanged; the facade does not check it.
BusinessKeyDefault — Business key stored against the legal follow-up record. Null or omitted is sent downstream as 0.
addToLegalFollowUp › Responses
Success.
This operation answers with HTTP 200 whether it succeeds or fails, so isSuccess has to be read. On failure errorCode and message carry the reason: a missing request or a zero MainCustomerNumber gives 60002 ParameterCannotBeNull; a business failure raised by the legal management service gives that service's own code and message; anything else gives the literal code UNHANDLED_ERROR and the exception's message. On success message is the fixed Turkish text "Takibe alma işlemi başarılı" and errorCode is absent.
The request cannot choose the channel, the user or the queue state. The facade fixes the channel to the system channel type, sets both the host name and the user name to the calling identity, and queues the record with status N.
responseTime is the server clock reading taken when the response object was built, not a value from the legal management service.
The call only queues the customer for legal follow-up; unlike Create Follow Up By Main Customer Number it does not close any card.
isSuccessWhether the operation did what it was asked to. A false here arrives with HTTP 200, so it has to be read rather than inferred from the status.
responseTimeA date and time as a string, in RFC 3339 form: 2026-10-16T14:30:00Z, or with an offset, 2026-10-16T17:30:00+03:00.
errorCodeThe platform's own code for the error, and what to match on.
messageThe error in words. errorCode is the part to match on.