This project is loan application system. Loan application process: The loan application process allows customers to apply for loans by filling out an online form that includes personal and financial information. Once the application is submitted, the system evaluates the application and assigns a loan limit based on the customer's creditworthiness.
Loan limit: The loan limit is the amount of money that a customer can borrow from the system. The loan limit is determined based on the customer's credit score, income, and other financial information.
Registration and login: To use the system, customers need to register and create an account. The registration process includes providing personal information such as name, address, and contact details. Once registered, customers can log in to their accounts using their username and password.
Loan request history: After logging in, customers can view their loan request history, including past and current loan applications. This feature helps customers keep track of their loan accounts and payment schedules.
Account management: Customers can update their account information, such as contact details, income, and name surname. They can also delete their account if they no longer want to use the system.
Loan approval process: Once a customer applies for a loan, the system reviews the application and approves or rejects it based on the customer's creditworthiness. The system also checks for any outstanding loans or pending loan requests by the customer.
Loan disbursement: If the loan application is approved, the system disburses the loan amount to the customer's bank account. The customer can then use the funds for the intended purpose, such as purchasing a car or paying for education.
Customer support: The loan application system provides customer support phone. Customers can reach out to the support team if they have any questions or concerns regarding their loan accounts.
Surety option: If a customer selects the surety option, they will need to provide information about the surety The system will create a surety object for the customer, which will be used to evaluate the loan application.
Collateral option: If a customer selects the collateral option, they will need to provide information about the collateral, including its value, location, and ownership details. The system will create a collateral object for the customer, which will be used to evaluate the loan application.
Both option: If a customer selects both options, they will need to provide information about both the surety and the collateral. The system will create a surety object and a collateral object for the customer, which will be used to evaluate the loan application.
By offering the surety, collateral, and both options, the loan application system provides more flexibility and customized loan solutions to customers based on their individual financial situation and creditworthiness.
- I used PCG algorithm for randomize credit score.
- PCG algorithm is a good choice for applications that require high-quality random numbers with low computational overhead. It is widely used in gaming, simulations, cryptography, and other areas where random numbers are needed.One of the key features of the PCG algorithm is that it uses a permutation of the output values to improve the statistical properties of the generated numbers. This means that the output values are not generated in a sequential or linear order, but rather in a randomly permuted order. This helps to reduce correlations between the generated numbers and improve their randomness.One of the key features of the PCG algorithm is that it uses a permutation of the output values to improve the statistical properties of the generated numbers. This means that the output values are not generated in a sequential or linear order, but rather in a randomly permuted order. This helps to reduce correlations between the generated numbers and improve their randomness.
- PCG vs other algorithms
-
Login Page
-
Register Page
-
Loan Apply Page
-
Update Profile Page
-
Delete Account Page
-
Find Loans
Frontend:
- JS (Programming Language),
- React(Frontend Framework),
- React-Router (Routing),
- Redux(predictable state container),
- TailwindCSS (CSS Framework),
- Axios (HTTP Client),
- Formik (Form Management),
Backend:
- Java 17 (Programming Language),
- Spring Boot (Backend Framework),
- Spring Security (Authentication and Authorization),
- Spring Data JPA (ORM),
- Spring Validation (Validation),
- Maven (Build Tool),
- H2 (In-Memory Database),
- Lombok (Code Generator),
- MapStruct (Object Mapper),
- OPENAPI (API Documentation),
- Hibernate (ORM),
- JUnit (Testing Framework),
- Mockito (Mocking Framework),
- AssertJ (Assertion Library),
- Hateoas (Hypermedia As The Engine Of Application State)
Database:
- PostgreSQL (Relational Database Management System)
- Because react is a JavaScript library for building user interfaces. It is maintained by Facebook and a community of individual developers and companies. React can be used as a base in the development of single-page or mobile applications. However, React is only concerned with rendering data to the DOM, and so creating React applications usually requires the use of additional libraries for state management and routing. Redux and React Router are respective examples of such libraries.
-
I think monolithic architecture can be a good choice for certain types of projects. For example, if the project has a relatively small codebase and a straightforward functionality, a monolithic architecture can simplify development and testing. Additionally, if the project does not require a lot of scalability and flexibility, a monolithic architecture can be easier to deploy and manage. Simplicity: Monolithic architecture is simpler to design, develop, and test than microservices. Since all the components of the system are contained within a single codebase, it is easier to understand how they interact and to maintain overall system consistency.
Performance: Monolithic architecture can provide faster performance than microservices, since all the components are running on a single server or set of servers. This reduces the overhead of network communication and can result in faster response times.
Easier deployment: Monolithic architecture is easier to deploy than microservices, since all the components are packaged together and can be deployed as a single unit. This can simplify deployment and make it more predictable.
Lower operational overhead: Monolithic architecture requires less operational overhead than microservices, since there are fewer moving parts and less complexity in the system. This can reduce the cost and effort required to maintain and support the system.
-
Relational databases are the most common type of database. They are based on the relational model, an intuitive, straightforward way of representing data in tables. Each row in the table is a record with a unique ID called the key. The columns of the table hold attributes of the data, and each record usually has a value for each attribute, making it easy to establish the relationships among data items.Relational databases have been widely used for many years, and they offer several advantages over other types of data storage systems. Some of the key advantages of relational databases include:
Data consistency and integrity: Relational databases use constraints and rules to enforce consistency and integrity of data. This ensures that the data is accurate, complete, and up-to-date.
Structured organization: Relational databases use a tabular structure, with each table containing rows of data and columns that represent specific attributes or properties. This structured organization makes it easier to manage and query large amounts of data.
Querying capabilities: Relational databases provide powerful query languages, such as SQL, that allow users to retrieve, filter, and sort data in a flexible and efficient way. This enables users to quickly and easily retrieve the information they need.
Scalability: Relational databases can be scaled vertically (by adding more resources to a single server) or horizontally (by adding more servers to a distributed system). This makes it possible to handle large amounts of data and accommodate increasing numbers of users.
Security: Relational databases provide a range of security features, including user authentication, access control, and encryption, to ensure that data is protected from unauthorized access or manipulation.
Overall, relational databases offer a reliable, flexible, and efficient way to manage and store large amounts of data. They are well-suited for applications that require high levels of data consistency, queryability, and security.
-
PostgreSQL is a popular open-source relational database management system that offers several advantages over other database systems. Extensibility: PostgreSQL has a modular architecture that allows developers to extend its functionality with custom data types, operators, and functions. This makes it a highly flexible and customizable database system.
Reliability: PostgreSQL is known for its high level of reliability and data integrity. It uses a multi-version concurrency control (MVCC) system that ensures that transactions are isolated and do not interfere with each other, reducing the risk of data corruption.
Scalability: PostgreSQL is designed to scale horizontally and vertically. It supports partitioning and clustering to distribute data across multiple nodes, and it can handle large volumes of data and high levels of concurrency.
ACID compliance: PostgreSQL is fully ACID compliant, which means that it ensures atomicity, consistency, isolation, and durability of transactions. This ensures that data is always in a consistent and valid state.
Rich feature set: PostgreSQL offers a rich set of features, including support for JSON, XML, and spatial data, as well as full-text search, advanced indexing, and transaction management.
Community support: PostgreSQL has a large and active community of developers and users who contribute to its development, documentation, and support. This community ensures that PostgreSQL is continuously improved and kept up-to-date with the latest technologies. Overall, PostgreSQL is a powerful and reliable database system that is well-suited for applications that require high levels of data consistency, reliability, and scalability. It offers a rich set of features and is highly extensible, making it a popular choice for developers and organizations of all sizes.
- The credit limit multiplier is 4 by default.
- [✅] New users can be defined in the system, existing customers can be updated or deleted.
- [✅] If the credit score is below 500, the user is rejected. (Loan result: REJECTED)
- [✅] If the credit score is between 500 points and 1000 points and the monthly income is below 5000
$, the user's loan application is approved and a limit of 10.000$ is assigned to the user. (Loan Result: APPROVED). - [✅] If he has given a guarantee, 10 percent of the amount of the guarantee is added to the credit limit.
- [✅] If the credit score is between 500 points and 1000 points and the monthly income is between 5000$ and 10,000 $, the user's loan application is approved and a 20,000 $ limit is assigned to the user. (Loan Result: APPROVED)
- [✅] If a guarantee has been given, 20 percent of the guarantee amount is added to the credit limit.
- [✅] If the credit score is between 500 points and 1000 points and the monthly income is above 10.000 $, the loan application of the user is approved and the user is assigned a limit of MONTHLY INCOME INFORMATION * CREDIT LIMIT MULTIPLIER/2. (Credit Result: APPROVED)
- [✅] If a guarantee is given, 25 percent of the guarantee amount is added to the credit limit.
- [✅] If the credit score is equal to or above 1000 points, the user is assigned a limit equal to MONTHLY INCOME * CREDIT LIMIT MULTIPLIER. (Credit Result: APPROVED)
- [✅] If the collateral is given, 50 percent of the collateral amount is added to the credit limit.
- [✅] As a result of the conclusion of the loan, the relevant application is recorded in the database.
- [✅] Afterwards, an informative SMS is sent to the relevant phone number and the approval status information ( rejection or approval), limit information is returned from the endpoint.
- [✅] A completed loan application can only be queried with the ID number and date of birth. If the date of birth and identity information do not match, it should not be questioned.
I added integration tests for controllers (to test the flow and API path) and unit tests for service layers by mocking.
All services and controllers are fully covered by tests.Happy case, empty case, validations, and null parameters tests
are written.
AVERAGE TEST COVERAGE IS 98%
The Singleton Pattern is a design pattern in software engineering that restricts the instantiation of a class to one object. This means that only one instance of the class can exist in the entire system. The purpose of the Singleton Pattern is to ensure that there is a single point of access to a specific object or resource, and to prevent multiple instances from being created, which can cause issues such as conflicting updates and inconsistent behavior.
To implement the Singleton Pattern, a class must have a private constructor that prevents the creation of new instances of the class from outside the class itself. The class also needs a static method that provides access to the single instance of the class. This method is responsible for creating the instance if it does not already exist and returning the existing instance if it does.
Singleton Pattern can be useful in scenarios such as database connections, logging services, and configuration settings, where there should only be one instance of the class throughout the application.
- I use it in the Logger class to create a single instance of the class.
The Factory Pattern is a design pattern in software engineering that provides a way to create objects without specifying the exact class of object that will be created. The purpose of the Factory Pattern is to separate the creation of objects from their use and to provide a single point of control for creating objects.
In the Factory Pattern, a factory class is used to create objects of a specific type. The factory class contains a method or methods that take parameters specifying the type of object to be created and any additional information needed to create the object. The factory class then creates and returns the appropriate object based on the parameters passed in.
One common implementation of the Factory Pattern is the use of a factory method. This is a method within a class that creates and returns an object of a specific type. The factory method may be static or non-static and may take parameters specifying the type of object to be created.
The Factory Pattern is often used in scenarios where the creation of objects is complex, or when the creation of objects needs to be controlled centrally. It is also useful when the exact class of object to be created is not known at the time of creation. Examples of applications that use the Factory Pattern include database access libraries, graphical user interface frameworks, and game engines.
- I used it in the notification service to create a notification object according to the type of notification.
The Command Pattern is a design pattern in software engineering that encapsulates a request as an object, thereby decoupling the sender of the request from the receiver. This allows for greater flexibility in the way requests are handled, and makes it possible to implement features such as undo/redo and queuing of requests.
In the Command Pattern, a command object is used to represent a specific request or action. The command object contains all the information necessary to execute the request, including a reference to the object that will perform the action. The sender of the request simply creates a command object and passes it to the receiver, which executes the command.
One of the benefits of the Command Pattern is that it allows for the separation of concerns between the sender and receiver of a request. The sender does not need to know anything about how the request will be handled or what actions will be taken, other than the fact that the command object will be executed. This allows for greater flexibility and modularity in the design of the system.
- I use it for the Guarantee Type Validation on SuretyValidationService and CollateralValidationService
The Facade Pattern is a design pattern in software engineering that provides a simplified interface to a complex system of classes, libraries or APIs. The purpose of the Facade Pattern is to provide a unified and simplified interface to a complex subsystem, making it easier to use and reducing the overall complexity of the system.
In the Facade Pattern, a facade object is created that provides a simplified interface to a complex subsystem. The facade object wraps one or more classes or libraries, providing a simplified interface to their functionality. The facade object may also provide additional functionality that is not available in the subsystem itself.
One of the benefits of the Facade Pattern is that it reduces the coupling between the client code and the subsystem. Since the client code only interacts with the facade object, it does not need to know about the internal details of the subsystem. This makes it easier to maintain and modify the subsystem without affecting the client code.
- I used it in the LoanController to hide the complexity of the loan application process.
The Builder Pattern is a design pattern in software engineering that provides a way to create complex objects in a step-by-step manner. The purpose of the Builder Pattern is to separate the construction of a complex object from its representation, allowing the same construction process to create different representations. One of the benefits of the Builder Pattern is that it allows for the creation of complex objects without requiring the client code to know the details of the construction process. The client code simply calls the appropriate methods on the builder object, and the object is constructed automatically. This makes it easier to use complex objects and reduces the likelihood of errors. In the Builder Pattern, a builder object is used to create a complex object. The builder object contains a series of methods that add components or features to the object being built. These methods are typically named in a way that makes the construction process easy to understand, such as "setFoo()" or "addBar()".
- For example, I use it in the Notification class to create a SmsDTO object.
The Chain of Responsibility Pattern is a design pattern in software engineering that provides a way to handle a request through a series of processing objects. The purpose of the Chain of Responsibility Pattern is to decouple the sender of a request from its receivers, allowing multiple objects to handle the request without the sender needing to know which object will handle it.
In the Chain of Responsibility Pattern, a chain of processing objects is created. Each processing object contains a reference to the next processing object in the chain, forming a linked list. When a request is received, the first processing object in the chain attempts to handle it. If the first processing object is unable to handle the request, it passes it on to the next processing object in the chain, and so on, until the request is handled or the end of the chain is reached.One of the benefits of the Chain of Responsibility Pattern is that it allows for greater flexibility in the way requests are handled. Since multiple processing objects can be added to the chain, it is possible to change the way requests are handled by modifying the chain. This makes it easier to add or remove processing objects as needed, and allows for more dynamic behavior in the system.
- I use it for the profiling user
The Strategy Pattern is a design pattern in software engineering that defines a family of interchangeable algorithms, encapsulates each one, and makes them interchangeable within a context object. The purpose of the Strategy Pattern is to allow the selection of an algorithm at runtime without modifying the context object that uses it.
In the Strategy Pattern, a context object is created that contains a reference to a strategy object. The strategy object contains an algorithm that can be used by the context object to perform a certain task. The context object is designed to be flexible, allowing different strategy objects to be used interchangeably.
One of the benefits of the Strategy Pattern is that it promotes the principle of separation of concerns. Since each strategy object encapsulates a different algorithm, it is possible to isolate and encapsulate different concerns in different objects. This makes it easier to maintain and modify the system over time, and reduces the likelihood of errors.
- I use it for the calculation based by for customer profile
The Observer Pattern is a design pattern in software engineering that defines a one-to-many dependency between objects, such that when one object changes state, all its dependents are notified and updated automatically. The purpose of the Observer Pattern is to provide a way to notify interested objects when a certain event occurs, without tightly coupling the objects together.
In the Observer Pattern, there are two main types of objects: the subject and the observers. The subject is the object that is being observed, and it maintains a list of all the observers that are interested in its state. When the state of the subject changes, it notifies all its observers by calling a method on each one. The observers then update their state accordingly.
One of the benefits of the Observer Pattern is that it allows for greater flexibility in the way objects are updated.
Since multiple observers can be added to the subject, it is possible to change the behavior of the system by adding or
removing observers as needed. This makes it easier to modify the system over time, and allows for more dynamic behavior.
I use it for the notification service to send notification to the user
Spring Boot provides built-in support for transactions through the Spring Framework's transaction management capabilities. Transactions ensure that a group of database operations are executed as a single unit of work, either succeeding or failing as a whole.
Spring Boot's transaction management features make it easy to manage transactions declaratively using annotations. Here are some key concepts to keep in mind:
Transactions are managed by the underlying transaction manager, which can be either a JDBC-based manager or a JTA-based manager.
Transactions can be managed programmatically using the TransactionTemplate class or declaratively using annotations such as @Transactional.
The @Transactional annotation can be applied to methods or classes, and allows you to specify the transactional behavior of the method or class.
The @Transactional annotation supports various attributes, such as propagation, isolation, timeout, and read-only, which allow you to customize the behavior of the transaction. The @Transactional annotation in Spring Boot supports several types of transactional behavior that can be customized according to the needs of your application. Here are some of the most commonly used types of transactional behavior:
REQUIRED: This is the default behavior of @Transactional. If a transactional method is called within the scope of an existing transaction, it will be executed within that transaction. If there is no existing transaction, a new transaction will be created.
REQUIRES_NEW: This type of behavior always creates a new transaction, even if an existing transaction is already in progress. When the method is complete, the new transaction is committed independently of any outer transactions.
MANDATORY: This type of behavior requires that an existing transaction already be in progress when the method is called. If there is no existing transaction, a TransactionRequiredException will be thrown.
NEVER: This type of behavior ensures that no transaction is in progress when the method is called. If an existing transaction is in progress, a TransactionException will be thrown.
SUPPORTS: This type of behavior allows the method to execute within an existing transaction, but also allows it to be executed outside of a transaction.
NOT_SUPPORTED: This type of behavior ensures that the method is executed outside of any existing transaction. If a transaction is already in progress, it is suspended for the duration of the method call.
NESTED: This type of behavior creates a nested transaction within an existing transaction. If an existing transaction is in progress, the nested transaction will be executed within the scope of the outer transaction. If the nested transaction fails, only the nested transaction is rolled back, not the outer transaction.
- For example:
{
"data": {
"value": {
"name": "John",
"surname": "Doe",
"identityNo": 88198508850,
"birthDate": "1998-12-31",
"phoneNumber": "5655355556",
"personType": "CUSTOMER",
"monthlyIncome": 5000,
"customerLimit": 0,
"baseAdditionalFieldsCreatedDate": "2023-02-27T11:25:10.671+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T11:25:10.671+00:00",
"links": [
{
"rel": "deleteCustomerById",
"href": "http://localhost:8082/api/v1/customer"
}
]
},
"serializationView": null,
"filters": null
},
"responseDate": "2023-02-27T11:25:49.837+00:00",
"message": null,
"success": true
}
You can reach Insomnia request set from here
- CREDIT SCORE
http://localhost:8081/api/v1/credit-scoreGETNO REQUEST BODY
RESPONSE BODY
{
"creditScore": 486,
"customerIdentityNo": 1
}
- SUCCESSFULLY LOGIN:
http://localhost:8082/auth/loginPOST
REQUEST BODY
{
"identityNo":88056746318,
"password": "123MmM"
}
RESPONSE BODY
{
"data": "Bearer eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiI0NDA2IiwiaWF0IjoxNjc3NDc5NDE3LCJleHAiOjE2Nzc1NjU4MTd9.dW-k40No-ONnu-6i30RNYGBpER0iXrVaJ0tGJgeXGLmoyNLcxF2-2jue5M_02UDWWenttUTUoh8N1jUuU0w8EA",
"responseDate": "2023-02-27T06:30:17.024+00:00",
"message": null,
"success": true
}
- FAILED LOGIN:
REQUEST BODY
{
"identityNo":88056546318,
"password": "123MmM"
}
RESPONSE BODY
{
"data": {
"errorDate": "2023-02-27T06:39:42.940+00:00",
"message": "Customer Identity No Invalid!",
"detail": "Please check the identity no."
},
"responseDate": "2023-02-27T06:39:42.940+00:00",
"message": "Customer Identity No Invalid!",
"success": false
}
- WRONG PASSWORD:
REQUEST BODY
{
"identityNo": 88198508850,
"password": "113MmM"
}
RESPONSE BODY
{
"data": {
"errorDate": "2023-02-27T06:41:06.000+00:00",
"message": "Password Invalid!",
"detail": "Please check the password."
},
"responseDate": "2023-02-27T06:41:06.000+00:00",
"message": "Password Invalid!",
"success": false
}
- Missing Password:
REQUEST BODY
{
"identityNo": 88198508850
}
RESPONSE BODY
{
"type": "about:blank",
"title": "Bad Request",
"status": 400,
"detail": "Failed to read request",
"instance": "/auth/login"
}
- REGISTER:
http://localhost:8082/auth/register
POST
REQUEST BODY
{
"name": "John",
"surname": "Doe",
"identityNo": 88056746318,
"birthDate": "1999-01-01",
"phoneNumber": "5125245556",
"personType": "CUSTOMER",
"monthlyIncome": 5000.0,
"password": "123MmM"
}
RESPONSE BODY
{
"data": {
"name": "John",
"surname": "Doe",
"identityNo": 88056746318,
"birthDate": "1999-01-01",
"phoneNumber": "5125245556",
"personType": "CUSTOMER",
"monthlyIncome": 5000.0,
"customerLimit": 0.0,
"baseAdditionalFieldsCreatedDate": "2023-02-27T06:30:11.825+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T06:30:11.825+00:00"
},
"responseDate": "2023-02-27T06:30:11.921+00:00",
"message": null,
"success": true
}
- FAILED REGISTER: IDENTİTY NO NOT UNIQUE
{
"data": {
"errorDate": "2023-02-27T06:42:51.326+00:00",
"message": "Customer Identity No Must Be Unique!",
"detail": "Please check the identity no of the customer."
},
"responseDate": "2023-02-27T06:42:51.326+00:00",
"message": "Customer Identity No Must Be Unique!",
"success": false
}
- FAILED REGISTER: IDENTİTY NO NOT NOT VALID
{
"data": {
"errorDate": "2023-02-27T06:43:23.708+00:00",
"message": "Customer Identity No Invalid!",
"detail": "Please check the identity no."
},
"responseDate": "2023-02-27T06:43:23.708+00:00",
"message": "Customer Identity No Invalid!",
"success": false
}
- FAILED REGISTER: PHONE NUMBER NOT UNIQUE
{
"data": {
"errorDate": "2023-02-27T06:44:04.274+00:00",
"message": "Customer Phone Number Must Be Unique!",
"detail": "Please check the phone number."
},
"responseDate": "2023-02-27T06:44:04.274+00:00",
"message": "Customer Phone Number Must Be Unique!",
"success": false
}
* FAILED REGISTER: PHONE NUMBER NOT VALID
```agsl
{
"data": {
"errorDate": "2023-02-27T06:44:37.000+00:00",
"message": "Customer Phone Number Invalid!",
"detail": "Please check the phone number."
},
"responseDate": "2023-02-27T06:44:37.000+00:00",
"message": "Customer Phone Number Invalid!",
"success": false
}
- FAILED REGISTER: CUSTOMER NAME FIELD IS NULL
{
"data": {
"errorDate": "2023-02-27T11:53:05.635+00:00",
"message": "Customer Fields Cannot Be Null!",
"detail": "Please be sure that all fields are entered."
},
"responseDate": "2023-02-27T11:53:05.635+00:00",
"message": "Customer Fields Cannot Be Null!",
"success": false
}
- FAILED REGISTER: MONTHLY INCOME IS NEGATIVE
{
"data": {
"errorDate": "2023-02-27T11:53:54.605+00:00",
"message": "Monthly Income Cannot Be Negative!",
"detail": "Please check the monthly income."
},
"responseDate": "2023-02-27T11:53:54.605+00:00",
"message": "Monthly Income Cannot Be Negative!",
"success": false
}
- UPDATE CUSTOMER SUCCESSFULLY REQUEST
http://localhost:8082/api/v1/customer
PUT
REQUEST BODY
{
"name": "Updated John 65",
"surname": "Doe",
"identityNo": 66079804482,
"birthDate": "1999-01-01",
"phoneNumber": "2555555555",
"personType": "CUSTOMER",
"monthlyIncome": 5000.0
}
RESPONSE BODY
{
"data": {
"name": "Updated John 65",
"surname": "Doe",
"identityNo": 74701447228,
"birthDate": "1999-01-01",
"phoneNumber": "2555555555",
"personType": "CUSTOMER",
"monthlyIncome": 4000,
"customerLimit": 0,
"baseAdditionalFieldsCreatedDate": "2023-02-27T12:02:57.468+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T12:03:06.484+00:00"
},
"responseDate": "2023-02-27T12:03:06.491+00:00",
"message": null,
"success": true
}
- WHEN CUSTOMER ID NOT FOUND
{
"data": {
"errorDate": "2023-02-27T06:47:16.123+00:00",
"message": "Customer Not Found!",
"detail": "Please check the id of the customer."
},
"responseDate": "2023-02-27T06:47:16.123+00:00",
"message": "Customer Not Found!",
"success": false
}
- WHEN IDENTITY NOT VALID
{
"data": {
"errorDate": "2023-02-27T12:03:48.634+00:00",
"message": "Customer Not Found!",
"detail": "Please check the id of the customer."
},
"responseDate": "2023-02-27T12:03:48.634+00:00",
"message": "Customer Not Found!",
"success": false
}
* WHEN MONTHLY INCOME NOT VALID
```agsl
{
"data": {
"errorDate": "2023-02-27T12:04:40.732+00:00",
"message": "Monthly Income Cannot Be Negative!",
"detail": "Please check the monthly income."
},
"responseDate": "2023-02-27T12:04:40.732+00:00",
"message": "Monthly Income Cannot Be Negative!",
"success": false
}
- DELETE CUSTOMER
http://localhost:8082/api/v1/customer
NO REQUEST BODY
{
"data": null,
"responseDate": "2023-02-15T16:13:20.259+00:00",
"message": null,
"success": true
}
- GET CUSTOMER
http://localhost:8082/api/v1/customer
GET
NO REQUEST BODY
RESPONSE BODY
{
"data": {
"value": {
"name": "John",
"surname": "Doe",
"identityNo": 48764713606,
"birthDate": "1999-12-22",
"phoneNumber": "5657555556",
"personType": "CUSTOMER",
"monthlyIncome": 5000,
"customerLimit": 0,
"baseAdditionalFieldsCreatedDate": "2023-02-27T06:12:28.467+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T06:12:28.467+00:00",
"links": [
{
"rel": "deleteCustomerById",
"href": "http://localhost:8082/api/v1/customer"
}
]
},
"serializationView": null,
"filters": null
},
"responseDate": "2023-02-27T06:49:22.388+00:00",
"message": null,
"success": true
}
- FIND LOAN SUCCESSFUL REQUEST
http://localhost:8082/api/v1/customer/{identityNo}/{birthday}/find-loans
GET
NO REQUEST BODY
{
"data": [
{
"paybackGuaranteeType": "COLLATERAL",
"amount": 0,
"result": "REJECTED",
"baseAdditionalFieldsCreatedDate": "2023-02-27T06:13:28.424+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T06:13:28.424+00:00"
},
{
"paybackGuaranteeType": "COLLATERAL",
"amount": 20400,
"result": "APPROVED",
"baseAdditionalFieldsCreatedDate": "2023-02-27T06:13:31.757+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T06:13:31.757+00:00"
},
{
"paybackGuaranteeType": "ALL_OF_THEM",
"amount": 0,
"result": "REJECTED",
"baseAdditionalFieldsCreatedDate": "2023-02-27T11:29:19.826+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T11:29:19.826+00:00"
},
{
"paybackGuaranteeType": "COLLATERAL",
"amount": 10192.8,
"result": "APPROVED",
"baseAdditionalFieldsCreatedDate": "2023-02-27T11:34:50.956+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T11:34:50.956+00:00"
},
{
"paybackGuaranteeType": "SURETY",
"amount": 0,
"result": "REJECTED",
"baseAdditionalFieldsCreatedDate": "2023-02-24T09:57:15.330+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-24T09:57:15.330+00:00"
}
],
"responseDate": "2023-02-27T12:10:36.815+00:00",
"message": null,
"success": true
}
- INFORMATION MISMATCH CASE
{
"data": {
"errorDate": "2023-02-27T12:11:33.273+00:00",
"message": "Customer Information Mismatch!",
"detail": "Please make sure you have entered your information correctly."
},
"responseDate": "2023-02-27T12:11:33.273+00:00",
"message": "Customer Information Mismatch!",
"success": false
}
- NULL CASE
{
"data": [],
"responseDate": "2023-02-27T12:08:59.055+00:00",
"message": null,
"success": true
}
- APPLY LOAN
http://localhost:8082/api/v1/loan/apply
POST
- PAYBACK GUARANTEE TYPE: COLLATERAL SUCCESSFUL CASE
REQUEST BODY
{
"paybackGuaranteeType": "COLLATERAL",
"collateralType": "MONEY",
"collateralWorth": 1928.0
}
RESPONSE BODY
{
"data": {
"paybackGuaranteeType": "COLLATERAL",
"amount": 20385.6,
"result": "APPROVED",
"customerLimit": 131715.6,
"baseAdditionalFieldsCreatedDate": "2023-02-27T01:12:21.618+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T01:12:21.618+00:00"
},
"responseDate": "2023-02-27T02:55:45.435+00:00",
"message": null,
"success": true
}
- PAYBACK GUARANTEE TYPE: COLLATERAL WORTH MINUS VALUE CASE
`REQUEST BODY`
```agsl
{
"paybackGuaranteeType": "COLLATERAL",
"collateralType": "MONEY",
"collateralWorth": -1
}
RESPONSE BODY
{
"data": {
"errorDate": "2023-02-27T12:18:52.274+00:00",
"message": "Worth must be positive",
"detail": "Please enter a positive value for worth"
},
"responseDate": "2023-02-27T12:18:52.274+00:00",
"message": "Worth must be positive",
"success": false
}
{
"paybackGuaranteeType": "COLLATERAL",
"collateralType": "MONEY",
"collateralWorth": -1
}
- PAYBACK GUARANTEE TYPE SURETY SUCCESSFUL CASE
`REQUEST BODY`
```agsl
{
"paybackGuaranteeType": "SURETY",
"suretyName": "Surety Jane",
"suretySurname": "Doe",
"suretyType": "JOINT",
"suretyIdentityNo": 47701739716,
"suretyBirthDate": "1980-01-01",
"suretyPhoneNumber": "55125559",
"suretyPersonType": "SURETY"
}
{
"suretyName": "Surety Jane",
"suretySurname": "Doe",
"suretyType": "JOINT",
"suretyIdentityNo": 47701739716,
"suretyBirthDate": "1980-01-01",
"suretyPhoneNumber": "55125559",
"suretyPersonType": "SURETY",
"paybackGuaranteeType": "SURETY"
}
RESPONSE BODY
{
"data": {
"paybackGuaranteeType": "SURETY",
"amount": 0,
"result": "REJECTED",
"customerLimit": 0,
"baseAdditionalFieldsCreatedDate": "2023-02-27T12:21:08.787+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-27T12:21:08.787+00:00"
},
"responseDate": "2023-02-27T12:21:08.799+00:00",
"message": null,
"success": true
}
- PAYBACK GUARANTEE TYPE SURETY PHONE NUMBER IS NOT UNIQUE CASE
{
"data": {
"errorDate": "2023-02-27T00:22:03.177+00:00",
"message": "Surety Phone Number Must Be Unique!",
"detail": "Please check the phone number."
},
"responseDate": "2023-02-27T00:22:03.178+00:00",
"message": "Surety Phone Number Must Be Unique!",
"success": false
}
- PAYBACK GUARANTEE TYPE SURETY IDENTITY NUMBER IS NOT UNIQUE CASE
{
"data": {
"errorDate": "2023-02-27T12:22:23.604+00:00",
"message": "Surety Identity No Must Be Unique!",
"detail": "Please check the identity no of the surety."
},
"responseDate": "2023-02-27T12:22:23.604+00:00",
"message": "Surety Identity No Must Be Unique!",
"success": false
}
- PAYBACK GUARANTEE TYPE SURETY IDENTITY NUMBER IS NOT VALID CASE
{
"data": {
"errorDate": "2023-02-27T12:23:04.088+00:00",
"message": "Surety Identity No Invalid!",
"detail": "Please check the identity no."
},
"responseDate": "2023-02-27T12:23:04.088+00:00",
"message": "Surety Identity No Invalid!",
"success": false
}
PAYBACK GUARANTEE TYPE BOTH OF THEM
REQUEST BODY
{
"suretyName": "Jane",
"suretySurname": "Doe",
"suretyType": "JOINT",
"suretyIdentityNo": 97898017852,
"suretyBirthDate": "1980-01-01",
"suretyPhoneNumber": "51665547",
"suretyPersonType": "SURETY",
"paybackGuaranteeType": "ALL_OF_THEM",
"collateralType": "MONEY",
"collateralWorth": 2000.0
}
RESPONSE BODY
{
"data": {
"paybackGuaranteeType": "ALL_OF_THEM",
"amount": 10200.0,
"result": "APPROVED",
"customerLimit": 20392.8,
"baseAdditionalFieldsCreatedDate": "2023-02-24T09:24:03.995+00:00",
"baseAdditionalFieldsUpdatedDate": "2023-02-24T09:24:03.995+00:00"
},
"responseDate": "2023-02-24T09:24:04.012+00:00",
"message": null,
"success": true
}
If you have any feedback, please reach out to us at [email protected]