/customers/{customer_id}/fundings/You must put the word
BearerorTokenin theAuthorizationheader before your token e.g:Authorization: Bearer <Your API token>Examples generated from this schema may be missing the word
Bearer.
The unique customer_id used to represent a customer.
Success
The total number of fundings for this customer. (May be more than appear in the items list due to pagination).
Identifies the application this funding resulted from
The amount transferred to the customer
The time at which the customer initiated the sending of the funds. This is usually when the funds were sent, except in cases where there was a delay.
The amount added on to the loan as a fee for this funding. This corresponds to the funding_amount and offer_fee_percentage.
A unique identifier for this funding
The duration of the loan. The end date of the loan is this many days from the first funding. (Later fundings from the same offer will show the same offer_duration_in_days, but are due to be repaid by the same time as the original funding).
What percentage of the amount borrowed was added to the loan as a fee when the customer took the money
Identifies the formal offer that the customer accepted. The fields offer_max_amount, offer_monthly_interest_percentage, offer_fee_percentage and offer_duration_in_days will be the same for fundings that have the same offer_id, because these are properties of the offer. They correspond to fields in the /offers endpoint and are duplicated here for convenience.
The maximum funding the customer can take from this offer.
Monthly interest rate as a percentage (e.g. 3.0 means 3% per month)