Workflow Parameter Definitions

The available parameters for each workflow step are described in the following sections. There are no parameters for the customer-account step.

notification

phoneNumber  REQUIRED

string

Customer’s mobile phone number. The LinX request is sent to this number via SMS.

channel

string enum, values: SMS

Notification method used to send the request to the Customer. If channel is not provided, the default value SMS will be used.

introductoryMessage

string

Introductory text to add to the beginning of the SMS message. If introductoryMessage is not provided, a default message will be used.

lookup-profile

customerId  REQUIRED

string (UUID)

ID of the Customer Account.

enhance-profile

If the enhance-profile step is included in the workflow, at least one of the following parameters is required.

personalInfo

array

Customer profile fields. Any or all of the following values can be provided:

  • salutation  Title before the Customer’s name (example: Dr).
  • dateOfBirth  Customer’s date of birth.

addresses

array

Customer’s address. Any or all of the following values can be provided:

  • SHIPPING
  • MAILING
  • PHYSICAL

phoneNumber

array

Customer’s phone number. One of the following values can be provided:

  • WORK
  • HOME

financial-account

financialAccountSubType  REQUIRED

string enum; values for BANK Financial Accounts: CHECKING, SAVING; values for CARD Financial Accounts: CREDIT, DEBIT

Financial Account subtype.

lookup-financial-account

customerFinancialAccountId  REQUIRED

string (UUID)

ID of an existing Customer Financial Account.

  • If transactionType is SEND, this account will receive funds from baFinancialAccountId.
  • If transactionType is REQUEST, this account will send funds to baFinancialAccountId.

document-acceptance

documents  REQUIRED

array

Documents to be accepted by the Customer.

documentId

string

Semantic document ID. Identifies the type of acceptance document.

documentGroup

string

Group to which the document belongs.

The following documents can be added to the document-acceptance step.

Document

documentId

documentGroup

Communications Consent Form

ebt-communication-consent bank-accounts

Privacy Policy

fncl-privacy-policy

rocket-financial

move-money

transactionType  REQUIRED

string enum, values: SEND, REQUEST

Type of transaction. The following values are supported:

  • SEND  Transfer funds from baFinancialAccountId to the Customer Financial Account. The Customer Financial Account is defined in financial-account (new Financial Account) or lookup-financial-account (existing Financial Account).
  • REQUEST  Transfer funds from the Customer Financial Account to baFinancialAccountId. The Customer Financial Account is defined in financial-account (new Financial Account) or lookup-financial-account (existing Financial Account).

solution  REQUIRED

string enum, values: push-to-card, ach, wire

RocketKOR solution used for the transaction.

baFinancialAccountId  REQUIRED

string (UUID)

ID of the second Financial Account to be used in the transaction.

  • If transactionType is SEND, this account will send funds to the Customer Financial Account. The Customer Financial Account is defined in financial-account (new Financial Account) or lookup-financial-account (existing Financial Account).
  • If transactionType is REQUEST, this account will receive funds from the Customer Financial Account. The Customer Financial Account is defined in financial-account (new Financial Account) or lookup-financial-account (existing Financial Account).

currency  REQUIRED

string

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

amount  REQUIRED

number

Amount of the transaction.

priority  CONDITIONAL

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

default value: IMMEDIATE

Required for ACH and Wire transactions.

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

  • IMMEDIATE  Near real-time.
  • SAME_DAY  Same business day.
  • NEXT_DAY  Next business day.
  • SCHEDULED  Reserved for future use.

Push to Card transactions always use the IMMEDIATE settlement priority.

description  CONDITIONAL

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.

paymentReasonId  REQUIRED

string

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

ON THIS PAGE
Exit mobile version