PushCoin can import student charges from a file. A CSV file with the columns described here can be provided to PushCoin via the admin console (under Billing > Queued charges) or through automated process (SFTP). The file includes charges to apply to student wallet or liability accounts. For example, you can automate pulling “student late fees”, “lost book” or “damaged Chromebook” entries from Destiny or Infosnap.
Important: If you plan on using the SFTP method, you must provide PushCoin with the IP address or the IP range from where the uploads will originate. Otherwise all SFTP connections will time out due to firewall policy.
The CSV file needs to be uploaded under this path and file-name:
<ACCOUNT_ID>/incoming/student_billing<_XXXX>.csv
The <_XXXX> placeholder in the filename can be omitted or used to name the source where the charges come from. Examples of valid filenames:
- student_billing.csv
- student_billing_destiny.csv
- student_billing_2017-02-12-library-fees.csv
[1] Mandatory fields are marked in red.
| Column name | Type | Description |
| account_type | String | Designates the account where the charge should be applied to. One of WALLET or LIABILITY. |
| charge_tracking_id | String | A unique identifier of the charge. PushCoin guarantees only one charge with this key will ever be applied to the student account regardless of how many times the file is uploaded.
For example, a UUID or concatenated fields like date, student ID, billing code can serve as charge_tracking_id. Max. 64 chars. |
| student_id | String | A unique student identifier within the district. Max. 64 chars. |
| billing_code | String | An identifier which maps to a product in PushCoin. Max. 64 chars. |
| note | String | (Optional) A short description of the charge other than the product or fee name which are already in PushCoin. For example: lost product’s serial number, book title, etc. Max. 255 chars. |
| amount | Decimal | (Optional) The amount to charge a student. If not provided, the amount will be the product price in PushCoin. |
| transaction_occurred_time | Datetime | (Optional) For older charges, this is the date and time when the transaction took place in the past. The date and time must be formatted according to ISO 8601. Example: 2017-05-03T14:38:02Z |