Exhibit A
Information for ACH NACHA file configuration
| File Header Record | ||||
| Field number | Field name | Description/questions | To be completed by the bank | |
| 2 | Priority code | The lower the number, the higher processing priority. Currently, defaulted to 01. Is this in alignment with your file implementation? | ||
| 3 | Immediate destination | The bank transit routing number preceded by a blank | ||
| 4 | Immediate origin | The Immediate Origin Field identifies the sender of the file. In these scenarios, this field is the Routing Number of the ODFI. Is this ok with the bank? | ||
| 11 | Immediate destination name | This is an optional field, anything specific that you would like us to enter in this field? | ||
| 12 | Immediate origin name | Mandatory. What name would you like us to enter in the field? | ||
| Batch header record | ||||
| Field number | Field name | Description/questions | To be completed by the bank | |
| 3 | Company name | The FinTech company name, up to 16 characters. This name May appear on the recipient’s statements prepared by the Receiving Financial Institution. Is it ok with the bank if we use the FinTech company name? | ||
| 5 | Company identification | Identical to the ‘Immediate origin’ used in File Header | ||
| 7 | Company Entry Description | Description of the transaction.This may be Printed on the recipient’s bank statement by the Receiving Financial Institution. (i.e. Payroll) Any specific information that the bank would like to enter? Otherwise we’ll leave it up to the FinTech | ||
| 12 | Originating Financial institution | We will enter your FI’s routing number |
Exhibit B
Information needed to establish cutoff and exchange times
| What is the end-of-day processing time? | Time / Time Zone |
| ACH Incoming File | Time |
| Cutoff | Time / Time Zone |
| ACH Outgoing File | |
| Same-Day ACH Early Cutoff | Time / Time Zone |
| Same-Day ACH Last Cutoff | Time / Time Zone |
| Standard ACH Cutoff | Time / Time Zone |
| Bank Holidays | Dates |
Exhibit C
Information needed to set up SFTP connection to process NACHA files
| Public SSH Key | SSH Key |
Exhibit D
Documents required for Mastercard Principal Membership
[coming soon]Exhibit E
BIN tokenization requirements
Each Issuer has certain requirements they need to fulfill in order to tokenize their BINs. Google Pay - Every bank needs to execute Google Pay Click to Accept Agreement Apple Pay - Every bank needs to execute:Exhibit F
MRDC requirements
In order for you to support Synctera MRDC functionality for your FinTech partners, you must complete a form for CheckAlt, Sycntera’s MRDC vendor:Exhibit G
Due diligence items and templates
- Review Synctera’s FinTech Risk and Compliance Launch Guide:
- Review the standard Risk and Compliance Launch Checklist that Synctera provides FinTechs:
- Review the Pre-Launch Documents (request from I&O specialist)
- Review Synctera’s Third Party Risk Management and Outsourcing Oversight Policy for reference, as necessary:
- Review Synctera’s Ground Control Program: