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
What is the point of having accounts field in MakePayments when recipientID is already required

Why do I have to supply the accounts information if I'm already supplying the recipientID for Make Payments endpoint? I already supplied the same accounts information when I created the recipient.

0
Posted 2 years ago
pic
⠿More
Draden Gaffney
30 × 3
Report
Votes Newest

Answers

My understanding is that multiple accounts can be listed for the same recipient that is why the account number is also required.

0
Posted 2 years ago
pic
⠿More
Trey Teter
489 × 4 Administrator
0

Why even create the recipient then in the first place if all the same fields are going to be asked when a payment is created? Seems redundant

— Draden Gaffney   2 years ago
Report
Write your answer
75 Views
1 Answer
2 years ago
2 years ago