The concept of technical debt in software development emerged by Cunningham (1992). Since then, this topic has been discussed and explored by several authors. There are types of technical debt corresponding to the phases of the software development cycle, such as requirements debt. This type of debt was initially mentioned by Ernst ( 2012), approximately 20 years after the introduction of the technical debt metaphor. This article aims to identify which are the strategies for payment requirements debt since the advent of the concept. The method used was literature review and content analysis with the application based on the PRISMA-P protocol, through descriptive research. The results, so far, reveal that there is still little discussion on the subject of technical debt of requirements. The main approach of the research refers to the types of technical debt of code and architecture.