Unanswered
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
- The
accountNumberfield refers to the account number that is used internally by the FI which I believe can be retrieved using theGetAccountListendpoint - The
clientAccountNumberfield 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) - The
emailAddressfield is required and would need to be passed in even if thealwaysSendEmailfield is set to false
Other
- The logonName in the Make Payment endpoint pertains to the sender
- If a payment is created but not authorized it will be marked as pending processing which can be verified via the
TransactionStatusfield in the Get Payments endpoint - 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
38 Views
0
Answers
3 years ago
3 years ago
@SoleneSossah can emailAddress be an empty string if the user has not set their email?
— Draden Gaffney 3 years agoHi Draden, I can bring this up to the team to see if modifications can be made, however, with the current implementation it appears that an email address is required for the request to go through.
— Solene Sossah 3 years ago