Skip to content
Learning

Credit card payment default prediction

Model next-month payment default

Use the UCI Default of Credit Card Clients dataset to classify the next monthly payment outcome. The saved network uses 23 inputs and is evaluated on 6,000 held-out customer records.

30,000Source records
23Encoded input values
6,000Testing-role records
1Model outputs

1. Business decision

Credit analysts can study how historical repayment and account descriptors associate with next-month default. The example demonstrates benchmark evaluation and error trade-offs; it does not estimate fraud or prescribe a lending decision.

Payment outcome

Keep next-month default distinct from transaction fraud.

Error trade-off

Review default sensitivity and false-positive costs.

Portfolio validation

Compare performance on later customer cohorts.

Credit analyticsRisk modellingModel validation
Historical customer-record classification for research and model evaluation.

2. Data set

The dataset contains 30,000 credit-card customer records. The identifier is excluded, and the target default_payment_next_month uses 1 for default and 0 for no default.

Source: Default of Credit Card Clients. Dataset license: CC-BY-4.0. The downloadable ZIP includes the adapted data and attribution notices.

Dataset measureSaved value
Analysis unitcustomer record
Records30,000
Raw variables24
Encoded model inputs23
Model outputs1
Training roles18000
Validation / selection roles6000
Testing roles6000
Unused roles0
FieldRoleTypeCategories
LIMIT_BALInputNumeric
SEXInputNumeric
EDUCATIONInputNumeric
MARRIAGEInputNumeric
AGEInputNumeric
PAY_0InputNumeric
PAY_2InputNumeric
PAY_3InputNumeric
PAY_4InputNumeric
PAY_5InputNumeric
PAY_6InputNumeric
BILL_AMT1InputNumeric
BILL_AMT2InputNumeric
BILL_AMT3InputNumeric
BILL_AMT4InputNumeric
BILL_AMT5InputNumeric
BILL_AMT6InputNumeric
PAY_AMT1InputNumeric
PAY_AMT2InputNumeric
PAY_AMT3InputNumeric
PAY_AMT4InputNumeric
PAY_AMT5InputNumeric
PAY_AMT6InputNumeric
default_payment_next_monthTargetBinary0, 1
Target class distribution pie chart
Target class distribution pie chart. Native Neural Designer report for this project.
The saved project assigns rows to training, validation and testing as shown above. This is internal record-level evaluation; it does not demonstrate separation by subject, device, site or acquisition batch.

3. Model

The model has 23 encoded inputs and 1 outputs. No architecture-selection experiment is recorded in this project. The diagram shows the topology used by the saved model.

LayerInput shapeOutput shapeActivation
Scaling2323
Dense233Tanh
Dense31Sigmoid

Output values are uncalibrated model scores. For binary evaluation, the saved positive class is 1.

Credit card payment default prediction — initial network architecture
Topology of the saved current model; no architecture selection is recorded.

4. Training strategy

The saved training configuration uses QuasiNewton with WeightedSquaredError.

Quasi-Newton method results

MeasureValue
Epochs number237
Elapsed time00:00:02
Stopping criterionMinimum loss decrease
Training error0.568
Validation error0.591
Quasi-Newton method error history
Quasi-Newton method error history. Native Neural Designer report for this project.

5. Model selection

No model selection experiment is recorded for this version. The validation subset guides fitting where a training report is present; it is distinct from the held-out test rows.

On this test subset a majority-class baseline would correctly classify 78.07% of the records. This baseline does not detect both classes and is not an optimized model.

6. Testing analysis

The figures and tables below refer to the current project’s saved testing analysis. The subset uses testing role 2; it contains 6000 source records.

ROC AUC describes ranking on this testing subset. Any optimal threshold shown in the saved ROC report was selected descriptively on that same subset; it is not an independently validated operating policy.

These operating-point metrics are calculated from the saved confusion counts at threshold 0.5. The positive-label coding is stated in the model section.

Confusion table

MeasurePredicted positivePredicted negativeTotal
Actual positive792 (13.2%)524 (8.7%)1316 (21.9%)
Actual negative954 (15.9%)3730 (62.2%)4684 (78.1%)
Total1746 (29.1%)4254 (70.9%)6000 (100.0%)
Test measureValue
Testing records6000
Positive cases1316
Positive prevalence21.93%
Accuracy75.37%
Sensitivity / recall60.18%
Specificity79.63%
Precision / PPV45.36%
F1 score0.517

Area under curve

MeasureValue
Area under curve0.772
ROC chart
ROC chart. Native Neural Designer report for this project.

7. Model deployment

Open the downloaded project in Neural Designer, inspect the dataset roles and preprocessing, then review the saved task report. Use the same input schema and category order when calculating outputs. The ZIP contains the exact current .nd, its source data and the applicable dataset notices.

Workflow: source measurements → schema and availability checks → model output → domain review. Keep model versions, validation evidence and incoming-data monitoring together.

8. Evidence and limitations

Internal row-level evaluation does not establish current portfolio performance, calibration or fair treatment across groups. Historical selection, policy and economic changes may shift the result. Human review and independent temporal, subgroup and calibration evaluation are required before individual lending decisions.

References