Visa Developer Community
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Ask the Community
Ajwah
Helper
February
Hi Diana, As developers we have better things to do than to be reading through the entire documentation from start to finish in order to keep track as to what has changed and figure out why things have changed. An API change log that we can RSS feed into would greatly reduce this work on our end. Next, the API documentation is currently lying. How can attributes that previously were marked as `conditional` be now marked as `optional`? In some cases those attributes were optional and in some cases those same attributes were required, so how can such attributes be classified as `optional`?
... View more
February
1 Kudo
Recently the API documentation for Visa Direct API changed in significant ways: -1 Addition of new optional fields, such as senderLastName, senderMiddleInitial etc. -2 Concept of attributes being conditional has been removed from the documentation. Fields are now either optional or either required. https://developer.visa.com/capabilities/visa_direct/reference?next=visa_direct__funds_transfer__v1__pushfunds#visa_direct__funds_transfer__v1__pushfunds I did not see a notification of any such changes and I am wondering if there is any API change log that would facilitate me in understanding: -1 What has changed -2 Why something has changed If there is an API change log, then kindly provide us with a link.
... View more
February
1 Kudo
https://developer.visa.com/capabilities/visa_direct/reference?next=visa_direct__funds_transfer__v1__pullfunds#visa_direct__funds_transfer__v1__pushfunds Under push transfer in above link, the attribute Surcharge states that it is only supported in the USA. Under pull transfer, the attribute Surcharge does not state this limitation. Question: Am I correct to assume that the limitation only pertains to Surcharge in the context of a push funds transfer and that such a limitation does not apply to a pull transaction?
... View more
February
1 Kudo
Hi Diana, From your response I have come to understand that those two attributes have no purpose/use case within the API request and thus can be regarded as non existent. Thank you for confirming that.
... View more
February
1 Kudo
https://developer.visa.com/capabilities/visa_direct/reference?next=visa_direct__funds_transfer__v1__pullfunds#visa_direct__funds_transfer__v1__pushfunds transactionCurrencyCode Required string | Length: 3 Use a 3-character alpha or numeric currency code for currency of the sender. You should (unless prohibited by local law / regulation) use the billingCurrencyCode obtained from the Funds Transfer Attribute Inquiry API under Payment Account Attribute Inquiry. Question: Can anyone be so kind to provide an example as to when one would be prohibited by local law/regulation to use the billingCurrencyCode obtained from the Funds Transfer Attribute Inquiry API?
... View more
February
1 Kudo
https://developer.visa.com/capabilities/paai/reference#paai__paai__v2__fundstransferinquiry Among the request attributes are the optional fields acquiringBin and acquirerCountryCode. Question: Why would we ever bother to send these optional fields along if they are not going to provide any extra information? For example, sharingGroupCode is an optional field, but by providing it, it will cause the API response with extra details about the various networks involved. In the case of the other two optional fields, there does not seem to be any extra information that gets provided when using them, so why would we ever use them?
... View more
February
Hi @vkamboj, Thank you for the clarrification, that was very helpful. I have looked at the JPG and that clarrified things for me. I would like to pursue three follow up questions on this: There is a disjunct between the API documentation that states the length of the field is 30 characters long whereas the VISA API Sandbox is not constrained accordingly. You are able to submit 1 character and it will accept that. So I believe there is either a need to update the documentation to change the length of the field to varying, between 1-30 characters or either there is a need for the VISA API Sandbox to be updated to reflect the constraint of exactly 30 characters, right padded with spaces as need be. If I wanted to utililze three different networks, say, CU24, Accel, and NYCE would I specify: "C E F " or would I specify "CEF "? And in what order would these networks be utilized, I assume from left to right? If I wanted to send through Pulse, I have three letters, S, L and H. How and why would I choose one letter over the other? Where can I find the information about the differences between S,L and H for instance?
... View more
February 2018
1 Kudo
Hi Diana, Thanks for the feedback. I am aware of the relationship between the attributes amount, surcharge and foreignExchangeFeeTransaction. It is stated in the documentation for amount: The amount of the transaction, inclusive of all fees you assess for the transaction, including currency conversion fees. If the originator is populating the surcharge or foreignExchangeFeeTransaction field, they must be included in the amount field. Regardless as to all of that, the issue I reported still stands, namely that the Sandbox API currently does not support 3 fraction digits. It only supports 2 fraction digits. Next, after further research into the matter, I came to understand that for Visa to be accepting a static amount of fraction digits would be deceiving, as that should be currency dependent. Currencies define their own minor digits. For example, the smallest currency denomination for USD is cents, 100 cents make up 1 dollar, so USD as a currency can have at most 2 minor digits. Other currencies, such as Iranian Rial, IRR do not have any minor digits, so to send an amount of 1.5 in such cases would be nonsensical. http://www.unicode.org/cldr/charts/dev/supplemental/detailed_territory_currency_information.html#IRR As such, I believe that the documentation needs to be updated on part of the attributes: amount, s urcharge and foreignExchangeFeeTransaction that the amount of fractional digits depend on the currency. Also, since it pertains to currencies, the correct terminology should be 'minor digits' as opposed to 'fractional digits'.
... View more
February 2018
1 Kudo
Below is the amount field as it appears in relevant documentation: https://developer.visa.com/capabilities/visa_direct/reference?next=visa_direct__funds_transfer__v1__pullfunds amount Required decimal | Length: totalDigits 12, fractionDigits 3 (minimum value is 0) The amount of the transaction, inclusive of all fees you assess for the transaction, including currency conversion fees. If the originator is populating the surcharge or foreignExchangeFeeTransaction field, they must be included in the amount field. As you can see, it states that the minimum value is 0. However, when I utilize the VISA Sandbox API and input 0 as value, it errors out: {"errorMessage": "API Validation Error: 3001. Mandatory field 'Amount' is missing or has invalid content."} If there is anything I am overlooking, then kindly clarify. If the API documentation is incorrect, then kindly update that the minimum value is 0.01 If the VISA Sandbox is incorrect, then kindly fix it.
... View more
February 2018
1 Kudo
Below is the surcharge field as documented here: https://developer.visa.com/capabilities/visa_direct/reference?next=visa_direct__funds_transfer__v1__pullfunds surcharge Optional Decimal | Length: totalDigits12, fractionDigits 3 (minimum value is 0) When present, this field contains the sender's surcharge as assessed by the originator. Values in this field must be in the same currency and format as defined in the amount field. It states that it can have 3 fraction digits, but in actual fact the sandbox api only allows 2 fraction digits. an otherwise valid request, when it has the field like this: "surcharge": "3.451" returns an error response: {
"errorMessage": "API Validation Error: 3001. Mandatory field 'Surcharge' is missing or has invalid content."
} Either I am misunderstanding something, so kindly clarify accordingly. Either there is a mistake with the VISA Direct documentation, kindly update. Either there is a mistake with the VISA Sandbox, kindly fix.
... View more
February 2018
1 Kudo
https://developer.visa.com/request_response_codes#network_id_and_sharing_group_code Here is the description at: https://developer.visa.com/capabilities/visa_direct/reference#visa_direct__funds_transfer__v1__pullfunds sharingGroupCode Optional string | Length: 30 This field is optionally used by Push Payments Gateway participants (merchants and acquirers) to specify the network access priority. Refer to Sharing Group Code Note: Supported only in US for domestic transactions involving Push Payments Gateway Service. QUESTIONS: Why is it of length 30 whereas it is only like one letter long? Is the formatting of the documentation messed up or so? When you look at the row: Pulse 0009 0017 0019 S L H is the sharing group code I need to send for Pulse "S L H", or can I choose any of the three letters? If the latter, then how do I choose one letter over the other? Why are certain fields bolded?
... View more
February 2018
1 Kudo
Thanks for the reply. I understand now where I am misunderstanding. My point of confusion was that I thought that the Push Payments Gateway Service was just a fancy name for the OCT Push transaction under the FundsTransfer API. Apparently, it is a separately classified service altogether, as the VISA docs is using the same terminology to explain as follows: The Funds Transfer API also supports the Visa Push Payments Gateway Service (PPGS) which allows originators to send PullFundsTransactions (AFTs) and PushFundsTransactions (OCTs) to multiple U.S. debit networks. Visa PPGS offers clients the following benefits: PPGS is provided through the Funds Transfer API by fillling out some extra fields in the Funds Transfer API, which includes both AFT and OCT. As it encompasses both AFT and OCT, it is clear that their naming is rather confusing. A better naming might have been: Auxilliary Networks Funds Transfer Service as empowered through Funds Transfer API.
... View more
February 2018
1 Kudo
Under the pull funds api: https://developer.visa.com/capabilities/visa_direct/reference?next=visa_direct__funds_transfer__v1__pullfunds the following field is mentioned: merchantPseudoAbaNumber Optional string | Length: 9 This is a number that uniquely identifies the originator when they sign up to send Push Payment Gateway transactions. On enrollment, an originator will get a single pseudo-value that is assigned by Visa. The other networks will assign their own unique values for the originator. Note: Supported only in US for domestic transactions involving Push Payments Gateway Service. Question: Since the note clarifies that it only pertains to transactions involving Push Payments Gateway Service, am I correct to assume that this field does not belong under the pull API documentation? If I am incorrect, then kindly clarify why the note singles out Push Payments Gateway Service.
... View more
February 2018
1 Kudo
Thank you for the link to the sample code. Even though it is classified under /legacy, the example does highly indicate that a FIPS code is to be used. However, I would like to be 100% certain about this and it seems to be that the documentation is not precise on the matter. Next, the matter of state code is still remaining. In the example documentation you linked to, the value 'CA' is utilized. This is highly inconsistent as a FIPS code is 5 digits long, 3 for county 2 for state. So to utilize the FIPS code for county, but to use something else for state is highly confusing.
... View more
February 2018
1 Kudo
Hi Diana, Could you be so kind as to provide me with a direct link to the example code you provided? I am not able to see it anywhere in the documentation. Could you be so kind as to provide me with a direct link to the VISA Direct documentation that explicitly states that county/state fields within cardAcceptor attribute are FIPS codes? Could you kindly clarify what ISO Country codes have to do with my question? Thanks.
... View more
February 2018
1 Kudo
https://developer.visa.com/capabilities/visa_direct/reference#visa_direct__funds_transfer__v1__pullfunds At the right side in the link above, the visa documentation provides a handy API interaction tool: https://www.dropbox.com/s/jyqoiopy3ih4vv7/Screenshot%202018-02-06%2018.57.30.png?dl=0 For cardAcceptorAddressCounty however, it provides the value: " San Mateo " whereas the documentation states: county Conditional string | Length: 3 Note:county of the money transfer operator/Originator. Required if cardAcceptor:address:country is "US". Questions: Am I correct to assume that the API call value: " San Mateo " is invalid? Am I correct to assume that the value instead should be a FIPS county code? Am I correct to assume that likewise the value for cardAcceptorState is invalid, as it is " state " : " CA " whereas it is supposed to be the FIPS state code instead?
... View more
January 2018
1 Kudo
Under request attributes of the API, with regards to the Address field for cardAcceptor attribute at: https://developer.visa.com/capabilities/visa_direct/reference#visa_direct__funds_transfer__v1__pushfunds The field zipCode states: string | minimum 5, maximum 9, Length: 5 - 9 Zip/Postal code of the money transfer operator/Originator. Required if cardAcceptor:address:country is "US" or "CA". Question 1: What exactly is a money transfer operator? The confusion stems from the fact that the other address fields are stating: Merchant/Originator, so the usage of a third terminology here would suggest that Money Transfer Operator is inherently different from Merchant, so you would have all the fields filled in with respect to a Merchant address details and for zipCode you would fill in the details of Money Transfer Operator. Question 2: Am I correct to understand that the reason as to why options Merchant/Originator are provided for the address fields, is to accommodate for the money transfer scenario? In such a case, the sender's name is to be taken and for address we would provide the Originator's address? Question 3: What exactly is the difference between Merchant and Originator? Am I correct to understand that the Merchant is any third party company integrating to our API whereas an Originator in this context would be our company itself making use of our API to directly provide for instance money transfer services to the public?
... View more
Public Statistics
| Date Registered | January 2018 |
| Date Last Visited | |
| Total Messages Posted | 17 |
| Total Kudos Received | 15 |
Latest Tags
No tags yet