SLT Schedule Object

A single-leg transaction (SLT) schedule is used to automatically execute single-leg transactions at a future date and time. You can use an SLT schedule to execute a one-time transaction or a series of recurring transactions.

The SLT Schedule object represents information for an SLT schedule. This includes information for the schedule (such as the ID, name, start date, recurrence rule, and status) and for the transaction(s) that will be created by the schedule such as the Financial Accounts, currency, and transaction amount).

Attributes

createdBy

object

Entity that created the SLT schedule.

id

string (UUID)

ID of the entity. Will be blank if createdBy.type is internal.

type

string enum, values: employee, internal, kor_employee, service-account

Type of entity. The following values are supported:

  • employee  Team Member using the RocketKOR Portal.
  • internal  Internal service call.
  • kor_employee  Rocket Financial employee.
  • service-account  Service Account using APIs.

createdAt

string (date-time), format: yyyy-MM-dd’T’HH:mm:ss.SSSz

Date and time the SLT schedule was created.

updatedBy

object

Entity that last updated the SLT schedule.

id

string (UUID)

ID of the entity. Will be blank if updatedBy.type is internal.

type

string enum, values: employee, internal, kor_employee, service-account

Type of entity. The following values are supported:

  • employee  Team Member using the RocketKOR Portal.
  • internal  Internal service call.
  • kor_employee  Rocket Financial employee.
  • service-account  Service Account using APIs.

updatedAt

string (date-time), format: yyyy-MM-dd’T’HH:mm:ss.SSSz

Date and time the SLT schedule was last updated.

startDateTime  

string, pattern: ^[0-9]{4}-(0[1-9]|1[0-2])-(0[1-9]|[1-2][0-9]|3[01])T([01][0-9]|2[0-3]):([0-5][0-9]):([0-5][0-9])(\.[0-9]{1,6})?$

Date and time to initiate the SLT schedule. Must be provided in the following ISO 8601 format without the time zone designator:

year-month-dayThours:minutes:seconds[.fractions-of-second]

where:

  • year is four digits
  • month is two digits
  • day is two digits
  • T is the literal “T” character used to delimit a date portion from a time portion
  • hours is two digits representing the number of hours from 00 to 23
  • minutes is two digits representing the number of minutes from 00 to 59
  • seconds is two digits representing the number of seconds from 00 to 59
  • fractions-of-second (optional) is one or more digits representing a fraction of a second

Example: 2023‐08‐31T15:53:00.123

The date will be interpreted using the timeZone parameter, and UTC format will be used if timeZone is not provided.

For recurring transactions, this is the date and time when the recurrenceRule will take effect. For example, let’s say a request has the following parameters:

"startDateTime": "2023-08-31T12:00:00",

"recurrenceRule: "FREQ=WEEKLY;BYDAY=MO"

In this example, the start date is on a Thursday and the recurrence rule is weekly executions each Monday. Therefore the first transaction will be created on Monday, September 4th, at 12:00 pm in the specified time zone.

timeZone

string

Time zone for startDateTime. The following values are supported:

  • Z, GMT, UTC or UT for the UTC time zone
  • zone offsets from UTC starting with + or – (example: +4)
  • zone offsets from UTC starting with UTC+, UTC+, GMT+, GMT-, UT+ or UT-
  • any other ID is parsed as an IANA Time Zone Database region ID (example: the value for America/New_York is -04)

calendarType

string enum, values: BANKING, DEFAULT

Type of calendar to use for the SLT schedule.

  • BANKING  Scheduled transactions will not be executed on a non-banking day, such as weekends and holidays, based on the country where the Business Account is legally identified.
  • DEFAULT  Scheduled transactions will execute on any day, including non-banking days. Note that this may result in errors depending on the day the transaction is executed and the solution/provider used for the transaction.

recurrenceRule

string

Rule used to schedule transactions on a recurring basis. Must be specified using the IETF iCalendar RFC 5545 RRULE property.

For example, let’s say a request has the following parameters:

"timeZone": "America/New_York",

"startDateTime": "1997-09-02T09:00:00",

"recurrenceRule": "FREQ=DAILY;UNTIL=19971224T000000"

This request will create transactions at the following times:

September 2, 1997 to October 25, 1997 (inclusive) at 9:00 AM EDT

October 26, 1997 to December 23, 1997 (inclusive) at 9:00 AM EST

name  

string, max length: 60

Name of the SLT schedule. Required if recurrenceRule is provided.

status

string enum, values: SCHEDULED, ACTIVE, SUSPENDED, DELETED, FINISHED

Status of the SLT schedule.

id  

string (UUID)

ID of the SLT schedule.

schedulerId

string (UUID)

ID of the scheduling system for the SLT schedule.

maskedDebitAccountNumber

string

Masked account number of the debit Financial Account.

maskedCreditAccountNumber

string

Masked account number of the credit Financial Account.

originatingChannel

string enum, values: EXTERNAL, INTERNAL, PORTAL

Channel used to create the SLT schedule. Possible values are:

  • EXTERNAL  RocketKOR APIs.
  • INTERNAL  Internal service call.
  • PORTAL  Team Member using the RocketKOR Portal.

transactionSpec  

object

Details for the transaction(s) created by the SLT schedule.

metadata  

string, max items: 6, value max length: 1024

Key/value pairs used to store additional information about the transaction. ACH transactions must include one or more of the following metadata parameters.

Parameter

Description

rkorACHEntryType

Required for all ACH transactions.

ACH Standard Entry Class (SEC) code. The following codes are supported. For more information, see ACH File Details.

  • ARC  Accounts Receivable Entry
  • BOC  Back Office Conversion
  • CCD  Cash Concentration or Disbursement
  • CIE  Customer Initiated Entry
  • CTX  Corporate Trade Exchange
  • IAT  International
  • POP  Point of Purchase Entry
  • PPD  Prearranged Payment and Deposit Entry
  • RCK  Re-Presented Check Entry
  • TEL  Telephone-Initiated Entry
  • WEB  Internet Initiated Entry

rkorACHIndividualId

Required if rkorACHEntryType is CIE, PPD, or TEL. Individual Identification Number.

rkorACHCheckSerialNumber

Required if rkorACHEntryType is ARC, BOC, POP, or RCK. Serial number of the check from a Converted Check Copy.

rkorACHTerminalCity

Required if rkorACHEntryType is POP. Terminal city.

rkorACHTerminalState

Required if rkorACHEntryType is POP. Terminal state.

The following metadata parameters are returned in the response.

Parameter

Description

rkorProvider

ACH Provider. Possible values are PAYGEARS and SNB.

rkorReasonCode

Return Reason Code. Present in RETURN transaction responses.

rkorReasonDescription

Return Reason Description. Present in RETURN transaction responses.

rkorDiscretionaryData

Return Transaction Identifier. Present in RETURN transaction responses.

debitFinancialAccountId  

string (UUID)

ID of the Financial Account used as the debit account (source of funds) for the transaction.

creditFinancialAccountId  

string (UUID)

ID of the Financial Account used as the credit account (receiver of funds) for the transaction.

transactionType  

string enum, values: SEND, REQUEST

Type of transaction. The following values are supported:

  • SEND  Push funds from the debit Financial Account to the credit Financial Account.

    For example, a SEND transaction would be used if a Business Account (owner of the debit Financial Account) is sending a refund to a Customer (owner of the credit Financial Account).

  • REQUEST  Pull funds to the credit Financial Account from the debit Financial Account.

    For example, a REQUEST transaction would be used if a Business Account (owner of the credit Financial Account) is collecting a rent payment from a Customer (owner of the debit Financial Account).

solution  

string

Name of the RocketKOR solution used for the transaction.

paymentReasonId  

string

ID representing the payment reason for the transaction. Use the Payment Reasons API to retrieve a list of available IDs.

amount

string (decimal)

Transaction amount.

  • The amount must conform to any transaction limits.
  • Either amount or debitBalancePercent is required. The request will fail if both parameters are provided.

debitBalancePercent

string (decimal)

Percentage of the debitFinancialAccountId balance to use as the transaction amount. Supports 4 decimal places. For example, to specify 12.25%, use the value 0.1225.

  • The amount must conform to any transaction limits.
  • Either amount or debitBalancePercent is required. The request will fail if both parameters are provided.

currency  

string

Currency used for the transaction. Must be an ISO 4217 alpha 3-character currency code.

settlementPriority

string enum, values: IMMEDIATE, SAME_DAY, NEXT_DAY, SCHEDULED

Required for ACH transactions. Optional for Wire transactions. Not required for Push-to-Card transactions.

Expected priority for settling the transaction. The following values are supported:

  • IMMEDIATE  Near real-time. Push-to-Card transactions always use the IMMEDIATE settlement priority. Not available for ACH And Wire transactions.
  • SAME_DAY  Same business day. Available for ACH And Wire transactions.
  • NEXT_DAY  Next business day. Available for ACH And Wire transactions.
  • SCHEDULED  Reserved for future use.

Note  If settlementPriority is not specified for ACH transactions, the value NEXT_DAY will be used.

description  

string, max length: 100

Required for the Wire solution. Not available for other solutions.

Brief description of the transaction. If the value exceeds the maximum length, the value will be truncated to 100 characters when the transaction is submitted for processing.

memo

string, max length: 100

Only available for the Wire solution.

Brief additional note about the transaction. If the value exceeds the maximum length, the value will be truncated to 100 characters when the transaction is submitted for processing.

initiatorAccountHolderId

string (UUID)

ID of the RocketKOR account that initiated the transaction. This can be a Business Account or a Customer Account.

SLT Schedule Object

				
					{
  "createdBy": {
    "id": "string(UUID)",
    "type": "employee | internal | kor_employee | service-account"
  },
  "createdAt": "string(date-time)",
  "updatedBy": {
    "id": "string(UUID)",
    "type": "employee | internal | kor_employee | service-account"
  },
  "updatedAt": "string(date-time)",
  "startDateTime": "string(date-time)",
  "timeZone": "string",
  "calendarType": "BANKING | DEFAULT",
  "recurrenceRule": "string",
  "name": "string",
  "status": "SCHEDULED | ACTIVE | SUSPENDED | DELETED | FINISHED",
  "id": "string(UUID)",
  "schedulerId": "string(UUID)",
  "maskedDebitAccountNumber": "string",
  "maskedCreditAccountNumber": "string",
  "originatingChannel": "EXTERNAL | INTERNAL | PORTAL",
  "transactionSpec": {
    "metadata": {
      "key": "value"
    },
    "debitFinancialAccountId": "string(UUID)",
    "creditFinancialAccountId": "string(UUID)",
    "transactionType": "SEND | REQUEST",
    "solution": "string",
    "paymentReasonId": "string",
    "amount": "string(decimal)", // amount or debitBalancePercent is returned
    "debitBalancePercent": "string(decimal)", // amount or debitBalancePercent is returned
    "currency": "string",
    "settlementPriority": "IMMEDIATE | SAME_DAY | NEXT_DAY | SCHEDULED",
    "description": "string",
    "memo": "string",
    "initiatorAccountHolderId": "string(UUID)"
   }
}

Step into the future of Finance with RocketKOR! Simplify payments, banking, lending, and data analytics using our versatile KOR Platform.

A Rocket Financial Inc. company

@ 2024 RocketKOR, Inc. All rights reserved.

Terms of Use     |     Privacy Policy
Exit mobile version