Peach Finance

Line of Credit Migration

Create past periods data

Creates past periods in preparation for migration.

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

Request Body schema: application/json
required
required
Array of objects (PastPeriodWithRequireds)
Responses
201

Success

post/people/{personId}/loans/{loanId}/migration/past-periods
Request samples
application/json
{
  • "pastPeriods": [
    ]
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": [
    ]
}

Update past period data

Updates past period in preparation for migration.

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

query Parameters
dueDate
required
string <date>

The due date of the period. The system will update the object corresponding to the period with a due date equal to dueDate. If no matching period is found, the system will not make any updates.

Request Body schema: application/json
required
id
string
createdAt
string <date-time>
updatedAt
string or null <date-time>
deletedAt
string or null <date-time>
startDate
string <date>

The period start date. The start date is inclusive.

endDate
string <date>

The period end date. The end date is inclusive.

statementDate
string <date>

The date when a statement for the period was created or should be created in the future.

dueDate
string <date>

The period's payment due date.

object or null
object (schemas-Statement)
Responses
200

Success

put/people/{personId}/loans/{loanId}/migration/past-periods
Request samples
application/json
{
  • "id": "string",
  • "createdAt": "2019-08-24T14:15:22Z",
  • "updatedAt": "2019-08-24T14:15:22Z",
  • "deletedAt": "2019-08-24T14:15:22Z",
  • "startDate": "2019-08-24",
  • "endDate": "2019-08-24",
  • "statementDate": "2019-08-24",
  • "dueDate": "2019-08-24",
  • "gracePeriod": {
    },
  • "statement": {
    }
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Delete past period data

Deletes past period in preparation for migration.

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

query Parameters
dueDate
required
string <date>

The due date of the period. The system will delete the object corresponding to the period with a due date equal to dueDate. If no matching period is found, the system will not make any updates.

Responses
204

Success no content

delete/people/{personId}/loans/{loanId}/migration/past-periods

Get past period data

Get past period in preparation for migration.

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

query Parameters
dueDate
string <date>

The due date of the period. The system will return the object corresponding to the period with due date equal to dueDate. If no matching period is found, the system will return no results.

startingAfter
string

Return results starting after the provided object identifier.

endingBefore
string

Return results ending before the provided object identifier.

reportingToAgency
string

Filters to only loan types set up to report to this agency.

Enum: "experian" "equifax" "transUnion" "innovis"
Responses
200

Past period data

get/people/{personId}/loans/{loanId}/migration/past-periods
Response samples
application/json
{
  • "status": 0,
  • "total": 0,
  • "count": 0,
  • "nextUrl": "string",
  • "previousUrl": "string",
  • "data": [
    ]
}

Get migration period LOC data

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

Responses
200

Migration period LOC data

get/people/{personId}/loans/{loanId}/migration/period
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Update migration period LOC data

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

Request Body schema: application/json
required
postMigrationLoanStatus
string
Default: "active"

The status of the line after a successful migration. If you pass accelerated or chargedOff, the system will first migrate the line as "active" and then immediately accelerate or charge off the line and its draws. The effectiveDate of the acceleration or charge off will be equal to the "migration cutoff date".

Enum: "active" "accelerated" "chargedOff"
postMigrationLoanChargedOffReason
string or null

The reason for the line charge off. Only required if migrationStatus=chargedOff.

  • term means the loan was charged off per loan type configuration after X days overdue.
  • fraudulent means the loan was charged off for a fraudulent reason.
  • bankruptcy means the loan was charged off because of bankruptcy.
  • legal means the loan was charged off because of some legal reason.
Enum: "term" "fraudulent" "bankruptcy" "legal"
object (MigrationPeriod)

The migration period. The "migration cutoff date" will be set to the startDate passed here. It's important to understand that migrationPeriod.statementDate and migrationPeriod.dueDate are future dates. The previous period's dueDate is also a future date (relative to when you execute the migration) and falls in the "migration period".

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024 Notes:
    • "Migration cutoff date" is Aug 1, 2024.
    • If you execute the migration on Aug 10, 2024, the "migration at date" is Aug 10.
    • Previous period's dueDate, Aug 22, 2024, falls in the "migration period" that starts on Aug 1, 2024 and ends on Aug 31, 2024.
    • The upcoming due date is Aug 22, 2024.
    • If you didn't complete the migration before Aug 22, 2024, you need to cancel the loan and start the process again.
object (LOCMigrationObligation)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the obligation object.

If you are migrating past periods:

This is the LOC level obligation details only (excluding any draws).

The data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should've already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the additional obligation data is part of the "Create migration period LOC data" vs "Create past periods data" endpoint.

To remind, the migration period is a "live" period in which you execute migration. The obligation details of the migration period will be calculated by the Peach system. Peach is also responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The obligation details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and other values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
object (LOCMigrationGracePeriod)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the gracePeriod object.

If you are migrating past periods:

This is the entire LOC grace period details including all its draws.

The grace period data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should have already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the grace period data is part of the "Create migration period LOC data" vs "Create past periods data" endpoint.

The migration period is a "live" period in which you execute migration.

  • Because the Peach system needs to know if the LOC is eligible for the grace period benefit when the migration period starts, the system will use the isGracePeriodEligible passed here. If you pass isGracePeriodEligible=true, the system will start migration without accruing interest in the "migration period". If you pass isGracePeriodEligible=false, the system will start migration with accruing interest in the "migration period".
  • On the "due date + 1" within the "migration period", the system evaluates the grace eligibility based on fullBalanceAmount, fullBalanceMinusOverdueAmount and payments made.
  • If you migrate the LOC before the upcoming "due date", the system will evaluate the grace period eligibility in "live" and might revoke the benefit.
  • If you migrate the LOC after the "due date", the system will evaluate the grace period eligibility as part of the "replay/migration" process. Because of existing limitations with "replay", grace period eligibility cannot be revoked as part of the replay process. However, the replay process can reinstate the grace period benefit (in other words, waive accrued interest from the start of the "migration period").
  • Peach is responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future. The grace period details of the migration period will be calculated by the Peach system on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024 Notes:
    • The grace period details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
object (LOCMigrationBalances)

The balances passed here should be as of the "migration cutoff date" after the most recent statement was generated in your legal system.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The balances should be as of Aug 1, 2024 after the statement was generated on Aug 1, 2024.
Responses
200

Migration period LOC data

put/people/{personId}/loans/{loanId}/migration/period
Request samples
application/json
{
  • "postMigrationLoanStatus": "active",
  • "postMigrationLoanChargedOffReason": "term",
  • "migrationPeriod": {
    },
  • "obligation": {
    },
  • "gracePeriod": {
    },
  • "balances": {
    }
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Create migration period LOC data

This endpoint allows you to pass additional details about the line in preparation for migration.

The "Migration period" is the period in which you execute the migration. This is the period from which the Peach system takes control over the line. This period is considered to be "open" at the time of the migration. The migration needs to be completed before the upcoming due date. To clarify, the upcoming due date corresponds to the previous period's statement date.

"Migration cutoff date" is the most recent statement date relative to the day on which you execute the migration process. This date is also the startDate of the migration period.

"Migration at date" is the actual date on which you execute the migration.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • "Migration cutoff date" is Aug 1, 2024.
    • If you execute the migration on Aug 10, 2024, the "migration at date" is Aug 10.
    • Previous period's dueDate, Aug 22, 2024, falls in the "migration period" that starts on Aug 1, 2024 and ends on Aug 31, 2024.
    • The upcoming due date is Aug 22, 2024.
  • If you didn't complete the migration before Aug 22, 2024, you need to cancel the loan and start the process again.
Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

Request Body schema: application/json
required
postMigrationLoanStatus
string
Default: "active"

The status of the line after a successful migration. If you pass accelerated or chargedOff, the system will first migrate the line as "active" and then immediately accelerate or charge off the line and its draws. The effectiveDate of the acceleration or charge off will be equal to the "migration cutoff date".

Enum: "active" "accelerated" "chargedOff"
postMigrationLoanChargedOffReason
string or null

The reason for the line charge off. Only required if migrationStatus=chargedOff.

  • term means the loan was charged off per loan type configuration after X days overdue.
  • fraudulent means the loan was charged off for a fraudulent reason.
  • bankruptcy means the loan was charged off because of bankruptcy.
  • legal means the loan was charged off because of some legal reason.
Enum: "term" "fraudulent" "bankruptcy" "legal"
required
object (MigrationPeriod)

The migration period. The "migration cutoff date" will be set to the startDate passed here. It's important to understand that migrationPeriod.statementDate and migrationPeriod.dueDate are future dates. The previous period's dueDate is also a future date (relative to when you execute the migration) and falls in the "migration period".

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024 Notes:
    • "Migration cutoff date" is Aug 1, 2024.
    • If you execute the migration on Aug 10, 2024, the "migration at date" is Aug 10.
    • Previous period's dueDate, Aug 22, 2024, falls in the "migration period" that starts on Aug 1, 2024 and ends on Aug 31, 2024.
    • The upcoming due date is Aug 22, 2024.
    • If you didn't complete the migration before Aug 22, 2024, you need to cancel the loan and start the process again.
required
object (LOCMigrationObligation)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the obligation object.

If you are migrating past periods:

This is the LOC level obligation details only (excluding any draws).

The data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should've already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the additional obligation data is part of the "Create migration period LOC data" vs "Create past periods data" endpoint.

To remind, the migration period is a "live" period in which you execute migration. The obligation details of the migration period will be calculated by the Peach system. Peach is also responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The obligation details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and other values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
required
object (LOCMigrationGracePeriod)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the gracePeriod object.

If you are migrating past periods:

This is the entire LOC grace period details including all its draws.

The grace period data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should have already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the grace period data is part of the "Create migration period LOC data" vs "Create past periods data" endpoint.

The migration period is a "live" period in which you execute migration.

  • Because the Peach system needs to know if the LOC is eligible for the grace period benefit when the migration period starts, the system will use the isGracePeriodEligible passed here. If you pass isGracePeriodEligible=true, the system will start migration without accruing interest in the "migration period". If you pass isGracePeriodEligible=false, the system will start migration with accruing interest in the "migration period".
  • On the "due date + 1" within the "migration period", the system evaluates the grace eligibility based on fullBalanceAmount, fullBalanceMinusOverdueAmount and payments made.
  • If you migrate the LOC before the upcoming "due date", the system will evaluate the grace period eligibility in "live" and might revoke the benefit.
  • If you migrate the LOC after the "due date", the system will evaluate the grace period eligibility as part of the "replay/migration" process. Because of existing limitations with "replay", grace period eligibility cannot be revoked as part of the replay process. However, the replay process can reinstate the grace period benefit (in other words, waive accrued interest from the start of the "migration period").
  • Peach is responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future. The grace period details of the migration period will be calculated by the Peach system on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024 Notes:
    • The grace period details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
required
object (LOCMigrationBalances)

The balances passed here should be as of the "migration cutoff date" after the most recent statement was generated in your legal system.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The balances should be as of Aug 1, 2024 after the statement was generated on Aug 1, 2024.
Responses
201

Migration period LOC data

post/people/{personId}/loans/{loanId}/migration/period
Request samples
application/json
{
  • "postMigrationLoanStatus": "active",
  • "postMigrationLoanChargedOffReason": "term",
  • "migrationPeriod": {
    },
  • "obligation": {
    },
  • "gracePeriod": {
    },
  • "balances": {
    }
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Get migration period draw data

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

drawId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The draw identifier.

Responses
200

Migration period draw data

get/people/{personId}/loans/{loanId}/draws/{drawId}/migration/period
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Update migration period draw data

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

drawId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The draw identifier.

Request Body schema: application/json
required
object (DrawMigrationObligation)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the obligation object.

If you are migrating past periods:

This is the draw level obligation details.

The draw level data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should have already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the draw level obligation data is part of the "Create migration period draw data" vs "Create past periods" endpoint.

To remind, the migration period is a "live" period in which you execute migration. The draw level obligation details of the migration period will be calculated by the Peach system. Peach is also responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The draw level obligation details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and other values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
object (DrawMigrationGracePeriod)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the gracePeriod object.

If you are migrating past periods:

This is the draw level grace period details.

The draw level grace period data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should have already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the draw level grace period data is part of the "Create migration period draw data" vs "Create past periods data" endpoint.

The migration period is a "live" period in which you execute migration.

  • Because the Peach system needs to know if the LOC is eligible for the grace period benefit when the migration period starts, the system will use the isGracePeriodEligible passed here. If you pass isGracePeriodEligible=true, the system will start migration without accruing interest in the "migration period". If you pass isGracePeriodEligible=false, the system will start migration with accruing interest in the "migration period".
  • On the "due date + 1" within the "migration period", the system evaluates the grace eligibility based on fullBalanceAmount, fullBalanceMinusOverdueAmount and payments made.
  • If you migrate the LOC/draw before the upcoming "due date", the system will evaluate the grace period eligibility in "live" and might revoke the benefit.
  • If you migrate the LOC/draw after the "due date", the system will evaluate the grace period eligibility as part of the "replay/migration" process. Because of existing limitations with "replay", grace period eligibility cannot be revoked as part of the replay process. However, the replay process can reinstate the grace period benefit (in other words, waive accrued interest from the start of the "migration period").
  • Peach is responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future. The grace period details of the migration period will be calculated by the Peach system on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The draw level grace period details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
object (DrawMigrationBalances)

The draw level balances passed here should be as of the "migration cutoff date" after the most recent statement was generated in your legal system.

We expect balances to include interest FOR the last date of the previous period (aka endDate) but not for the most recent statement date (which is also the first day of the migration period). For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The balances should be as of Aug 1, 2024 after the statement was generated on Aug 1, 2024.
    • End of day principal balance on Jul 31, 2024: $100.00.
    • The line/draw accrues daily simple interest of 18% annually (with 360 method).
    • The balances passed to Peach should include the daily interest that was accrued at the end of the day Jul 31, 2024:
    • $100.00 * (0.18 / 360) = $0.05
    • Peach system will accrue daily interest for the end of the day Aug 1, 2024 day balance and onward.
Responses
200

Migration period draw data

put/people/{personId}/loans/{loanId}/draws/{drawId}/migration/period
Request samples
application/json
{
  • "obligation": {
    },
  • "gracePeriod": {
    },
  • "balances": {
    }
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Create migration period draw data

This endpoint allows you to pass additional details about draws in preparation for migration.

The "migration period" is the period in which you execute the migration. This is the period from which the Peach system takes control over the line. This period is considered to be "open" at the time of the migration. The migration needs to be completed before the upcoming due date. To clarify, the upcoming due date corresponds to the previous period's statement date.

The "Migration cutoff date" is the most recent statement date relative to the day on which you execute the migration process. This date is also the startDate of the migration period.

The "Migration at date" is the actual date on which you execute the migration.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called 'past period'):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • 'Migration cutoff date' is Aug 1, 2024.
    • If you execute the migration on Aug 10, 2024, the 'migration at date' is Aug 10.
    • Previous period's dueDate, Aug 22, 2024, falls in the 'migration period' that starts on Aug 1, 2024 and ends on Aug 31, 2024.
    • The upcoming due date is Aug 22, 2024.
    • If you didn't complete the migration before Aug 22, 2024, you need to cancel the loan and start the process again.
Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

drawId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The draw identifier.

Request Body schema: application/json
required
required
object (DrawMigrationObligation)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the obligation object.

If you are migrating past periods:

This is the draw level obligation details.

The draw level data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should have already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the draw level obligation data is part of the "Create migration period draw data" vs "Create past periods" endpoint.

To remind, the migration period is a "live" period in which you execute migration. The draw level obligation details of the migration period will be calculated by the Peach system. Peach is also responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The draw level obligation details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and other values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
required
object (DrawMigrationGracePeriod)

If you are not migrating past periods and the migration period is the first period of the LOC:

Don't pass the gracePeriod object.

If you are migrating past periods:

This is the draw level grace period details.

The draw level grace period data passed here corresponds to the previous period and not to the migration period. By the time you call this endpoint, you should have already created one or more past periods. The additional data that you pass here is only required for the previous period and not for all past periods. That's why the draw level grace period data is part of the "Create migration period draw data" vs "Create past periods data" endpoint.

The migration period is a "live" period in which you execute migration.

  • Because the Peach system needs to know if the LOC is eligible for the grace period benefit when the migration period starts, the system will use the isGracePeriodEligible passed here. If you pass isGracePeriodEligible=true, the system will start migration without accruing interest in the "migration period". If you pass isGracePeriodEligible=false, the system will start migration with accruing interest in the "migration period".
  • On the "due date + 1" within the "migration period", the system evaluates the grace eligibility based on fullBalanceAmount, fullBalanceMinusOverdueAmount and payments made.
  • If you migrate the LOC/draw before the upcoming "due date", the system will evaluate the grace period eligibility in "live" and might revoke the benefit.
  • If you migrate the LOC/draw after the "due date", the system will evaluate the grace period eligibility as part of the "replay/migration" process. Because of existing limitations with "replay", grace period eligibility cannot be revoked as part of the replay process. However, the replay process can reinstate the grace period benefit (in other words, waive accrued interest from the start of the "migration period").
  • Peach is responsible for generating the statement corresponding to the migration period on migrationPeriod.statementDate in the future. The grace period details of the migration period will be calculated by the Peach system on migrationPeriod.statementDate in the future.

For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The draw level grace period details that you need to pass correspond to the previous period that started on Jul 1, 2024 and ended on Jul 31, 2024.
    • The amounts and values should be as of the "migration cutoff date", Aug 1, 2024, after the statement was finalized in your legacy system.
required
object (DrawMigrationBalances)

The draw level balances passed here should be as of the "migration cutoff date" after the most recent statement was generated in your legal system.

We expect balances to include interest FOR the last date of the previous period (aka endDate) but not for the most recent statement date (which is also the first day of the migration period). For example:

  • Migration period:
    • startDate: Aug 1, 2024
    • endDate: Aug 31, 2024
    • statementDate: Sep 1, 2024
    • dueDate: Sep 22, 2024
  • Previous period (also called "past period"):
    • startDate: Jul 1, 2024
    • endDate: Jul 31, 2024
    • statementDate: Aug 1, 2024
    • dueDate: Aug 22, 2024
  • Notes:
    • The balances should be as of Aug 1, 2024 after the statement was generated on Aug 1, 2024.
    • End of day principal balance on Jul 31, 2024: $100.00.
    • The line/draw accrues daily simple interest of 18% annually (with 360 method).
    • The balances passed to Peach should include the daily interest that was accrued at the end of the day Jul 31, 2024:
    • $100.00 * (0.18 / 360) = $0.05
    • Peach system will accrue daily interest for the end of the day Aug 1, 2024 day balance and onward.
Responses
201

Migration period draw data

post/people/{personId}/loans/{loanId}/draws/{drawId}/migration/period
Request samples
application/json
{
  • "obligation": {
    },
  • "gracePeriod": {
    },
  • "balances": {
    }
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Create past transaction

Creates past transaction in preparation for line of credit migration.

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

Request Body schema: application/json
required
One of:
id
string
createdAt
string <date-time>
updatedAt
string or null <date-time>
deletedAt
string or null <date-time>
type
required
string
Value: "oneTime"
externalId
string or null (externalId) <= 50 characters

A lender's identifier for a resource.

After the resource is successfully created, a lender can use the Peach assigned ID OR the externalId identifiers to fetch the resource.

Fetching with externalId:

To fetch a resource using an externalId, you MUST use the prefix ext- in the URL.

For example, a loan with an external identifier of ABCDE would be referenced like /api/people/BO-FAKE-IDNT/loans/ext-ABCDE.

Creating with externalId:

To create a resource with an external identifer, you MUST NOT use the prefix ext-.

For example, if the external identifier should be ABCDE, then pass { externalId: "ACBCE", ... } in the request body.

failureReason
string

The transaction failure reason. This value is ignored except when creating an external transaction with status=failed

Enum: "insufficientFunds" "chargeback" "accountClosed" "invalidAccount" "unknownReason" "invalidCvv" "invalidExpirationDate" "avsFailed" "networkError" "cardDeclined" "accountFrozen" "deceased" "invalidRouting" "paymentStopped" "incorrectNumber" "fraudulent" "unauthorizedDebit"
paymentInstrumentId
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

Peach's unique or lender's external identifier.

amount
required
number <float> >= 0

The amount of the payment.

evidenceDocumentId
string^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

Peach's unique or lender's external identifier.

status
required
string (PastTransactionCreationStatus)

The transaction status. May only be passed when isExternal=true.

External transactions can be created in: scheduled, initiated, pending, succeeded, or failed. External transactions are applied to the loan balance immediately when created with status initiated, pending, or succeeded. Otherwise, they will be applied the first time they are updated to one of these statuses.

initiated - payment was initiated and sent to a payment processor. The payment is applied to a loan. This status is used normally for ACH.

pending - payment was acknowledged by the payment processor and is being processed. For ACH the payment can be in pending status for a few days.

succeeded - payment was completed successfully.

failed - payment failed and was removed from the loan effective as of initiated, pending or succeeded status effective date. The system replays the loan as if the payment never happened. It will also re-accrue interest since then.

inDispute - payment is in dispute (typically because of chargeback). The payment is removed from the loan effective as of initiated, pending or succeeded status effective date. The system replays the loan as if the payment never happened. It will also re-accrue interest since then. Disputed payment can be for partial amount.

canceled - payment or credit was canceled. Payment can be canceled only if the current status is scheduled.

chargeback - payment was disputed and ruled against the lender. The payment was returned to the original payment instrument. Chargeback payment can be for partial amount.

Enum: "initiated" "pending" "succeeded" "failed" "canceled" "inDispute" "chargeback"
effectiveDate
required
string <date>

This attribute can be used only during the migration process of loans from another system to Peach. Any value passed for active loans will be ignored.

The effective date of the transaction in the product timezone. This attribute can be used for transactions with isExternal=true only. The date must be in the past or today. Make sure to provide effectiveTimeOfDay also.

required
object

The effective time of day on effectiveDate in the product timezone. This attribute can be used for transactions with isExternal=true only. Required if effectiveDate is passed.

Note: for migration only, the value must be after 2AM in the product timezone.

object

Payment instrument details are only allowed to be passed for migrated lines of credit. This allows you to create transactions without the need to create a payment instrument object first. If the paymentInstrumentDetails is passed, the system will not require paymentInstrumentId. Instead, the system will automatically create a payment instrument behind the scenes. The instrument will be created as instrumentType=paymentNetwork and mainly used to be displayed in the Borrower Portal or an App. The instrument cannot be used for any future transactions after the migration.

object

Transaction migration related details. This object:

  • Can be used only for transactions with an effective date before the "migration cutoff date".
  • Can be used for lines that are migrated from another system to Peach. Don't use it for installment loan migration.
  • Allows you to pass details on how a transaction was applied/allocated to draws.

For example:

Line of credit had three draws prior to the "migration cutoff date". Balances of draws were:

  • Draw A: $650
  • Draw B: $70
  • Draw B: $0

A payment of $120 was processed. Using this object you can tell the system that $120 was waterfalled/allocated as following:

  • Draw A split: $70
  • Draw B split: $50
  • Draw A split: $0

If you don't pass the migration object, then you won't be able to make the following status changes after the "migration cutoff date": pending → failed succeeded → failed

Responses
201

Created

post/people/{personId}/loans/{loanId}/migration/past-transaction
Request samples
application/json
{
  • "id": "string",
  • "createdAt": "2019-08-24T14:15:22Z",
  • "updatedAt": "2019-08-24T14:15:22Z",
  • "deletedAt": "2019-08-24T14:15:22Z",
  • "type": "oneTime",
  • "externalId": "string",
  • "failureReason": "insufficientFunds",
  • "paymentInstrumentId": "string",
  • "amount": 0,
  • "evidenceDocumentId": "string",
  • "status": "initiated",
  • "effectiveDate": "2019-08-24",
  • "effectiveTimeOfDay": {
    },
  • "paymentInstrumentDetails": {
    },
  • "migration": {
    }
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Get past transactions

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

query Parameters
status
Array of strings (TransactionStatusReadOnly)
Items Enum: "scheduled" "initiated" "pending" "succeeded" "failed" "canceled" "inDispute" "chargeback"
paymentInstrumentId
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The payment instrument identifier.

transactionType
string
Enum: "payment" "serviceCredit"
serviceCreditTypes
Array of strings (serviceCreditTypes)
Items Enum: "serviceAgent" "serviceSupervisor" "settlementOfDebt" "balanceTransfer" "refund" "fraud" "badDebt" "bankruptcy" "deceased" "usuryCap" "interestAdjustment" "rounding"
toEffectiveDate
string <date>

Last day for which an object's effective date must match

fromEffectiveDate
string <date>

First day for which an object's effective date must match

limit
integer [ 1 .. 100 ]
Default: 25

The maximum count of results to retrieve.

startingAfter
string

Return results starting after the provided object identifier.

endingBefore
string

Return results ending before the provided object identifier.

sortBy
Array of strings

The data attributes by which to sort the results.

Items Enum: "appliedAt" "+appliedAt" "-appliedAt" "createdAt" "+createdAt" "-createdAt" "effectiveDate" "+effectiveDate" "-effectiveDate"
Responses
200

Success

get/people/{personId}/loans/{loanId}/migration/past-transaction
Response samples
application/json
{
  • "status": 0,
  • "total": 0,
  • "count": 0,
  • "nextUrl": "string",
  • "previousUrl": "string",
  • "data": [
    ]
}

Update past transaction

Update past transaction in preparation for line of credit migration.

Note: After migration, you should call the "Update transaction" endpoint.

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

transactionId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

Transaction ID. Can be Peach or lender's external identifier.

Request Body schema: application/json
required
effectiveDate
string <date>

This attribute can be used only during the migration process of loans from another system to Peach. Any value passed for active loans will be ignored.

The effective date of the transaction in the product timezone. This attribute can be used for transactions with isExternal=true only. The date must be in the past or today. Make sure to provide effectiveTimeOfDay also.

object

The effective time of day on effectiveDate in the product timezone. This attribute can be used for transactions with isExternal=true only. Required if effectiveDate is passed.

Note: for migration only, the value must be after 2AM in the product timezone.

object

Payment instrument details are only allowed to be passed for migrated lines of credit. This allows you to create transactions without the need to create a payment instrument object first. If the paymentInstrumentDetails is passed, the system will not require paymentInstrumentId. Instead, the system will automatically create a payment instrument behind the scenes. The instrument will be created as instrumentType=paymentNetwork and mainly used to be displayed in the Borrower Portal or an App. The instrument cannot be used for any future transactions after the migration.

object

Transaction migration related details. This object:

  • Can be used only for transactions with an effective date before the "migration cutoff date".
  • Can be used for lines that are migrated from another system to Peach. Don't use it for installment loan migration.
  • Allows you to pass details on how a transaction was applied/allocated to draws.

For example:

Line of credit had three draws prior to the "migration cutoff date". Balances of draws were:

  • Draw A: $650
  • Draw B: $70
  • Draw B: $0

A payment of $120 was processed. Using this object you can tell the system that $120 was waterfalled/allocated as following:

  • Draw A split: $70
  • Draw B split: $50
  • Draw A split: $0

If you don't pass the migration object, then you won't be able to make the following status changes after the "migration cutoff date": pending → failed succeeded → failed

externalId
string or null (externalId) <= 50 characters

A lender's identifier for a resource.

After the resource is successfully created, a lender can use the Peach assigned ID OR the externalId identifiers to fetch the resource.

Fetching with externalId:

To fetch a resource using an externalId, you MUST use the prefix ext- in the URL.

For example, a loan with an external identifier of ABCDE would be referenced like /api/people/BO-FAKE-IDNT/loans/ext-ABCDE.

Creating with externalId:

To create a resource with an external identifer, you MUST NOT use the prefix ext-.

For example, if the external identifier should be ABCDE, then pass { externalId: "ACBCE", ... } in the request body.

amount
number <float> >= 0

The amount of the payment.

status
string (PastTransactionCreationStatus)

The transaction status. May only be passed when isExternal=true.

External transactions can be created in: scheduled, initiated, pending, succeeded, or failed. External transactions are applied to the loan balance immediately when created with status initiated, pending, or succeeded. Otherwise, they will be applied the first time they are updated to one of these statuses.

initiated - payment was initiated and sent to a payment processor. The payment is applied to a loan. This status is used normally for ACH.

pending - payment was acknowledged by the payment processor and is being processed. For ACH the payment can be in pending status for a few days.

succeeded - payment was completed successfully.

failed - payment failed and was removed from the loan effective as of initiated, pending or succeeded status effective date. The system replays the loan as if the payment never happened. It will also re-accrue interest since then.

inDispute - payment is in dispute (typically because of chargeback). The payment is removed from the loan effective as of initiated, pending or succeeded status effective date. The system replays the loan as if the payment never happened. It will also re-accrue interest since then. Disputed payment can be for partial amount.

canceled - payment or credit was canceled. Payment can be canceled only if the current status is scheduled.

chargeback - payment was disputed and ruled against the lender. The payment was returned to the original payment instrument. Chargeback payment can be for partial amount.

Enum: "initiated" "pending" "succeeded" "failed" "canceled" "inDispute" "chargeback"
failureReason
string (TransactionFailureReason)

The transaction failure reason.

Enum: "insufficientFunds" "chargeback" "accountClosed" "invalidAccount" "unknownReason" "invalidCvv" "invalidExpirationDate" "avsFailed" "networkError" "cardDeclined" "accountFrozen" "deceased" "invalidRouting" "paymentStopped" "microdepositsFailed" "microdepositsAttemptFailed" "incorrectNumber" "fraudulent" "unauthorizedDebit"
Responses
200

Success

put/people/{personId}/loans/{loanId}/migration/past-transaction/{transactionId}
Request samples
application/json
{
  • "effectiveDate": "2019-08-24",
  • "effectiveTimeOfDay": {
    },
  • "paymentInstrumentDetails": {
    },
  • "migration": {
    },
  • "externalId": "string",
  • "amount": 0,
  • "status": "initiated",
  • "failureReason": "insufficientFunds"
}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}

Get past transaction by ID

Securityoauth2 or bearerAuth or apiKeyHeader
Request
path Parameters
personId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

A Borrower's unique identifier, tied to a person or a business. Can be Peach or a lender's external identifier.

loanId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

The unique identifier of the Loan we wish to retrieve. Can be Peach or lender's external identifier.

transactionId
required
string (AnyId) ^ext-|^[A-Z][A-Z0-9]-[A-Z0-9]+-[A-Z0-9]+|^\d+...

Transaction ID. Can be Peach or lender's external identifier.

Responses
200

Success

get/people/{personId}/loans/{loanId}/migration/past-transaction/{transactionId}
Response samples
application/json
{
  • "status": 0,
  • "message": "string",
  • "data": {
    }
}
➔ Next to Expected Payments

Request sandbox access