/ach_funds_availability

Use this endpoint to find out the expected settlement time of funds into the Sila wallet of a single end user.

👍

Expected settlement time into Sila wallet

Note that this endpoint returns the expected settlement time into the Sila wallet, NOT the end user's RDFI. This is also the expected time - actual settlement time may differ.

This request takes either a list of already-submitted transactions OR a submitted_at time (future times allowed) and ach_type and returns the expected time those funds will settle into an end user's Sila wallet.

Request

Provide EITHER:

  • list of transactions
    OR
  • submission_time and ach_type

Authorization / Authentication

Use a valid access token in an Authorization: Bearer request header.

See Authenticating with an Access Token for more details.

POST /0.2/ach_funds_availability HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
Authorization: Bearer [GENERATED JWT TOKEN HERE]

{
  "header": {
    "created": 1234567890, //required
    "app_handle": "<your app_handle>", //required
    "user_handle": "<user_handle>",
    "version": "0.2", 
    "reference": "<your unique id>"
  }, 
  "transactions": ["list of transaction UUIDs"],
  "submission_time": 1234567890,
  "ach_type": "NEXT_DAY or SAME_DAY"
}

***

HTTP/1.1 202 OK

// If transactions supplied

{
  "success": True,
  "transactions": [
    {
      settlement_time: 1234567890,
      settlement_timestamp: 1234567890
    },
    {
      settlement_time: 1234567890,
      settlement_timestamp: 1234567890
    }
  ]
}

// If submission_type and ach_type supplied

{
  "success": True,
  "settlement_time": 1234567890,
  "settlement_timestamp": 1234567890
}

Request Attributes

KeyTypeDescription
headerJSON objectRequired.

Required keys:

created - Unix epoch timestamp in seconds. Must not be future-dated and must not be dated more than 5 minutes in the past.
app_handle - your app handle
user_handle - user_handle to pull funds for

Optional keys:

reference: Can be any value for your own reference. If not provided, one will be assigned.
version: Cannot be null if key is present. Valid values: 0.2, v0.2, V0.2
transactionsarray of stringsRequired if submission_type and ach_type are not supplied.

Array of transaction UUIDs. Can be found in response to whichever endpoint is used to create the transaction, or in /get_transactions.
submission_timedatetimeRequired along with ach_type if transactions not supplied.

Unix epoch timestamp for a past or future time - represents the creation time for the transaction.
ach_typestringRequired along with submission_time if transactions not supplied.

Valid options:

"NEXT_DAY"
"SAME_DAY"

Responses

Status CodeSuccess AttributeDescription
200true
400falseValidation error.
404falseIf you have passed transactions into the request and there is an invalid UUID: error that a transaction is incomplete.