LoanOffer class

Constructors

LoanOffer({required String uuid, required ProductType productType, required ProductSubType productSubType, String? productSubTypeDisclaimer, String? url, required Originator originator, String? originatorId, required bool preQualified, required bool preApproved, required bool secured, required bool coApplicant, required bool sponsored, required int maxAmount, int? minAmount, int? termLength, TermUnit? termUnit, String? displayTermUnit, String? termDescription, num? maxApr, num? minApr, num? meanApr, required AprType aprType, String? aprDescription, num? feeRate, num? maxFeeRate, num? minFeeRate, num? feeFixed, num? maxFeeFixed, num? minFeeFixed, required bool allowPrepayment, num? prepaymentFee, num? monthlyPayment, num? maxMonthlyPayment, num? minMonthlyPayment, String? monthlyPaymentDescription, num? meanMonthlyPayment, num? maxTotalPayment, num? minTotalPayment, num? meanTotalPayment, num? recommendationScore, num? payout, num? conversionProbability, String? terms, String? amountPrefix})

Returns a new LoanOffer instance.

Properties

allowPrepayment ↔ bool

getter/setter pair

amountPrefix ↔ String?

Some loan offers require a prefix (e.g. up to*) to be displayed to the left of the displayed loan amount. This is a nullable field that may be up to six characters long.

getter/setter pair

aprDescription ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

aprType ↔ AprType

getter/setter pair

coApplicant ↔ bool

getter/setter pair

conversionProbability ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

displayTermUnit ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

feeFixed ↔ num?

The maximum fee, in dollars, for an offer. maxFeeFixed should be used instead

getter/setter pair

feeRate ↔ num?

The maximum percent of loan amount fee for an offer. maxFeeRate should be used instead

getter/setter pair

hashCode → int

The hash code for this object.

no setter, override

maxAmount ↔ int

getter/setter pair

maxApr ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

maxFeeFixed ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

maxFeeRate ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

maxMonthlyPayment ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

maxTotalPayment ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

meanApr ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

meanMonthlyPayment ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

meanTotalPayment ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

minAmount ↔ int?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

minApr ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

minFeeFixed ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

minFeeRate ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

minMonthlyPayment ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

minTotalPayment ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

monthlyPayment ↔ num?

The estimated maximum monthly payment, in dollars, for an offer. maxMonthlyPayment should be used instead

getter/setter pair

monthlyPaymentDescription ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

originator ↔ Originator

getter/setter pair

originatorId ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

payout ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

preApproved ↔ bool

getter/setter pair

prepaymentFee ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

preQualified ↔ bool

getter/setter pair

productSubType ↔ ProductSubType

getter/setter pair

productSubTypeDisclaimer ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

productType ↔ ProductType

getter/setter pair

recommendationScore ↔ num?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

secured ↔ bool

getter/setter pair

sponsored ↔ bool

getter/setter pair

termDescription ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

termLength ↔ int?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

terms ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

termUnit ↔ TermUnit?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

url ↔ String?

Please note: This property should have been non-nullable! Since the specification file does not include a default value (using the "default:" property), however, the generated source code must fall back to having a nullable type. Consider adding a "default:" property in the specification file to hide this note.

getter/setter pair

uuid ↔ String

getter/setter pair

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toJson() → Map<String, dynamic>

toString() → String

A string representation of this object.

override

Operators

operator ==(Object other) → bool

The equality operator.

override

Static Methods

fromJson(dynamic value) → LoanOffer?

Returns a new LoanOffer instance and imports its values from value if it's a Map, null otherwise.

listFromJson(dynamic json, {bool growable = false}) → List<LoanOffer>

mapFromJson(dynamic json) → Map<String, LoanOffer>

mapListFromJson(dynamic json, {bool growable = false}) → Map<String, List<LoanOffer>>

Constants

requiredKeys → const Set<String>

The list of required keys that must be present in a JSON.