Hi Draden, The flow that you described above is valid. We don't currently support making ACH payments to unassociated accounts outside of these endpoints. **Create Recipient** 1. The `accountNumber` field refers to the account number that is used internally by the FI which I believe can be retrieved using the `GetAccountList` endpoint 2. The `clientAccountNumber` field doesn't appear to be utilized, we will make changes to our documentation to reflect this. In the meantime you may need to pass a random value while testing. Please keep a look out for upcoming releases in our changelog (https://docs.q2api.com/docs/q2-caliper-api/f1a95bb9397ba-changelog-for-caliper-api) 3. The `emailAddress` field is required and would need to be passed in even if the `alwaysSendEmail` field is set to false **Other** 1. The logonName in the Make Payment endpoint pertains to the sender 2. If a payment is created but not authorized it will be marked as pending processing which can be verified via the `TransactionStatus` field in the Get Payments endpoint 3. In terms of your question regarding fees, you can make up to 2000 API requests for free and additional requests can be purchased (see https://docs.q2api.com/docs/q2-caliper-api/729542264ca31-q2-caliper-api)

Hi Draden, The flow that you described above is valid. We don't currently support making ACH payments to unassociated accounts outside of these endpoints. **Create Recipient** 1. The `accountNumber` field refers to the account number that is used internally by the FI which I believe can be retrieved using the `GetAccountList` endpoint 2. The `clientAccountNumber` field doesn't appear to be utilized, we will make changes to our documentation to reflect this. In the meantime you may need to pass a random value while testing. Please keep a look out for upcoming releases in our changelog (https://docs.q2api.com/docs/q2-caliper-api/f1a95bb9397ba-changelog-for-caliper-api) 3. The `emailAddress` field is required and would need to be passed in even if the `alwaysSendEmail` field is set to false **Other ** 1. The logonName in the Make Payment endpoint pertains to the sender 2. If a payment is created but not authorized it will be marked as pending processing which can be verified via the `TransactionStatus` field in the Get Payments endpoint 3. In terms of your requestion regarding fees, you can make up to 2000 API requests for free and additional requests can be purchased (see https://docs.q2api.com/docs/q2-caliper-api/729542264ca31-q2-caliper-api)

Hi Draden, The flow that you described above is valid. We don't currently support making ACH payments to unassociated accounts outside of these endpoints. **Create Recipient** 1. The `accountNumber` field refers to the account number that is used internally by the FI which I believe can be retrieved using the `GetAccountList` endpoint 2. The `clientAccountNumber` field doesn't appear to be utilized, we will make changes to our documentation to reflect this. In the meantime you may need to pass a random value while testing. Please keep a look out for upcoming releases in our changelog (https://docs.q2api.com/docs/q2-caliper-api/f1a95bb9397ba-changelog-for-caliper-api) 3. The `emailAddress` field is required and would need to be passed in even if the `alwaysSendEmail` field is set to false **Other ** 1. The logonName in the Make Payment endpoint pertains to the sender 2. If a payment is created but not authorized it will be marked as pending processing which can be verified via the `TransactionStatus` field in the Get Payments endpoint 3. In terms of your question regarding fees, you can make up to 2000 API requests for free and additional requests can be purchased (see https://docs.q2api.com/docs/q2-caliper-api/729542264ca31-q2-caliper-api)

Hi Draden, The flow that you described above is valid. We don't currently support making ACH payments to unassociated accounts outside of these endpoints. **Create Recipient** 1. The `accountNumber` field refers to the account number that is used internally by the FI which I believe can be retrieved using the `GetAccountList` endpoint 2. The `clientAccountNumber` field doesn't appear to be utilized, we will make changes to our documentation to reflect this. In the meantime you may need to pass a random value while testing. Please keep a look out for upcoming releases in our changelog (https://docs.q2api.com/docs/q2-caliper-api/f1a95bb9397ba-changelog-for-caliper-api) 3. The `emailAddress` field is required and would need to be passed in even if the `alwaysSendEmail` field is set to false **Other** 1. The logonName in the Make Payment endpoint pertains to the sender 2. If a payment is created but not authorized it will be marked as pending processing which can be verified via the `TransactionStatus` field in the Get Payments endpoint 3. Regarding fees, you can make up to 2000 API requests for free and additional requests can be purchased (see https://docs.q2api.com/docs/q2-caliper-api/729542264ca31-q2-caliper-api) Please reach out if you have additional questions. Thanks, Solène