Verify applicant income from sources, not screenshots.

The applicant consents and logs in to a payroll, bank, or gig platform inside the screening flow. Burnt returns verified income fields and rent-to-income status against the property's criteria, typically within minutes of the connection. Your team reviews the result; the decision stays yours, made against the criteria you configured.

Yes. Income can be verified through gig platforms, payment platforms, and bank deposits as well as traditional payroll, so 1099 contractors and self-employed applicants are not screened out by a pay-stub-only process. Your team sees the same rent-to-income status either way, with the source method noted on each result.

Yes, structurally. A pay stub is a file the applicant controls and can edit, and document-fraud tools can only try to catch a fake after it is submitted. A source connection removes the file entirely: income comes from the payroll or bank system itself, so there is no document to forge in the first place.

The applicant signs in directly with their payroll or bank provider in a secure session. Credentials are never shared with you, your team, or your files, and no statements or pay stubs are transferred to your side. Because your property never holds the applicant's login or raw financial documents, there is no income PII in your records to lose.

Applicants who can't access a source login get a document-upload fallback inside the same flow, so the application keeps moving. Each result shows which method was used, so your team always knows whether income was source-verified or document-based before reviewing it against your criteria.