Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
How to send ACH payment using caliper api?

I'm trying to send a payment from a holding account that we own to a user. I wanted to get some clarity on steps that need to be taken and where certain data/inputs come from.

Overall steps:

  • Create recipient
  • Make Payment
  • Authorize

Questions for create recipient:
Where does accountNumber come from? Is that the same as AccountNumberInternal in getAccountList?
Where does clientAccountNumber come from? How is it different from accountNumber?
Can I supply an empty string for emailAddress especially since alwaysSendEmail is going to be set to false?

Questions for make payment:
Is the logonName the logonName of the recipient or the sender?

Am I missing anything in the process?

What happens if we never authorize a payment we created?

Are there any fees with this?

Is there an easier way to send funds from one account to another?

Posted 3 years ago
Votes Newest

Answers


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

0

@SoleneSossah can emailAddress be an empty string if the user has not set their email?

— Draden Gaffney   3 years ago
1

Hi 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