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
neiba
Helper
March
Hi! I attach another test that I made from postman where it also gives an error when sending the% character in the trackData field. Test done on postman Text Script Please someone will know what I'm missing? or if it is not possible to make payments with the trackData field? regards
... View more
March
Hi! I presented the same error and what I did was report the case in cybersource (support https://ebc2test.cybersource.com/ebc2/) and they enabled this functionality for my merchant Id. regards
... View more
March
hi, I need to know what restrictions the TrackData field has? I am using the Cybersource API and I try to make a present card type payment but the api is replying token error when sending in TrackData field. Do these VISA apis have any restrictions as to special characters? I did the tests with the example code that you provide with php and python and with both gives the same error when passing that field. Example of the data that I am passing: %B4111111111111111^SMITH/BETTY^30121200123456789012** XXX******?*;4111111111111111=30121200XXXX00000000?* Has someone made a Cybersource payment with present card and TrackData? Thank You
... View more
February
Hi! In the first answer the sandbox respond that trackData field is not valid, that answer is correct but in the second test the visa sandbox should respond equal (just add the percentage symbol) and it is not like that, because, the sandbox respond that token is not valid. It is important to mention that I am using the example code that provides a visa and that works properly for me in the realization of payments, capture, reverse authorization, etc. So far this is failing me when I try to make a payment sending the trackdata field with a %, and for the error it seems that there was some kind of restriction. For example, this trackData "=%B4111111111111111^SMITH/BETTY^30121200123456789012**XXX * *****? *; 4111111111111111 = 30121200XXXX00000000 ? *" is valid but I can not try from api visa because said token is not valid.
... View more
February
1 Kudo
Hi! I write you because I am try the API Cybersource Payments and I need to process a payment with point sale, but when I send trackData field, the response is it is not consistent because when I send this field without the percentage symbol it indicates that it is not valid, but when I send it with the percentage symbol, the api replies that the token is not valid. Could you please help me solve this error? Will you have an example code of payments through Visa using the Cybersource payment API? This is resquest example with %: { "clientReferenceInformation": { "code": "APIPAYMENT20190215104236" }, "processingInformation": { "commerceIndicator": "retail", "capture": true }, "orderInformation": { "amountDetails": { "totalAmount": "628.50", "currency": "USD" } }, "pointOfSaleInformation": { "cardPresent": "Y", "entryMode": "swiped", "terminalCapability": "2", "emv": { "fallback": "Y", "fallbackCondition": "1" }, "trackData": "B4111111111111111^SMITH\\/BETTY^30121200123456789012**\\nXXX******?*;4111111111111111=30121200XXXX00000000?*" } } Response: { "status": 400, "data": { "submitTimeUtc": "2019-02-15T14:50:41Z", "status": "INVALID_REQUEST", "reason": "INVALID_DATA", "message": "Declined - One or more fields in the request contains invalid data", "details": [ { "field": "pointOfSaleInformation.trackData", "reason": "INVALID_DATA" } ] } } This is a resquest example without %: { "clientReferenceInformation": { "code": "APIPAYMENT20190215104236" }, "processingInformation": { "commerceIndicator": "retail", "capture": true }, "orderInformation": { "amountDetails": { "totalAmount": "628.50", "currency": "USD" } }, "pointOfSaleInformation": { "cardPresent": "Y", "entryMode": "swiped", "terminalCapability": "2", "emv": { "fallback": "Y", "fallbackCondition": "1" }, "trackData": "%B4111111111111111^SMITH\\/BETTY^30121200123456789012**\\nXXX******?*;4111111111111111=30121200XXXX00000000?*" } } Response: { "status": 401, "data": { "responseStatus": { "status": 401, "code": "9159", "severity": "ERROR", "message": "Token validation failed", "info": "" } } } Thanks in advance, regards
... View more
January
Hello guy, I have the same issue and I don't find endpoin v2 to generateKey and Flex. I need to get v2 keys and generate v2 payment profiles. Can you help me?
... View more
December
Hi everyone, I have the same issus, when I try tokenizing the card info: request: <pre> { "keyId":"08BB06qeCtosikwD710XyXE9BZVLrdsq", "cardInfo":{ "cardNumber":"ry+Dj8iRBBzBn3n2uxtxdPGXP1HyWtAL2+dtzSAS9V46e2Z\/ERmdvF+GT+xRx8tHM1FcOUj1x7sOijkCkx8o5JyFAixbStOaLzQ9hSlOcCrXA6RSPn9SLSwlyZ2mKD5NYHkPArdjbBf9sZi8tetENB\/KMvQ\/GsOcLJdrqYSIed4Tm0s6nM1zvpIp3rRV844\/L8ZuyjXIytg6Gany3VkTdl7XMi6isj3EpLsAwVS7zJwcENEngLkexZPVq+Z9qr4b9Ezp2TwI\/Yx59lUHCBURmdb2fqda6mW8U9dBOCs6bcTYbJQVZdbG1zYhnx+ZzAro36QwxDeUGRH+mKMgdFWvKA==", "cardExpirationMonth":"4", "cardExpirationYear":"2019", "cardType":"001"} } Response <pre>"responseStatus": { "status": 400, "reason": "DECRYPTION_ERROR", "message": "Cannot decrypt PAN (RsaOaep256): data hash wrong", "correlationId": null, "details": [] }, Please, have you found any solution to this problem?
... View more
December
Hi everyone, I have the same issus, when I try tokenizing the card info: </pre> Response <pre> "responseStatus": { "status": 400, "reason": "DECRYPTION_ERROR", "message": "Cannot decrypt PAN (RsaOaep256): data hash wrong", "correlationId": null, "details": [] } </pre> Please, have you found any solution to this problem?
... View more
June
1 Kudo
I am look the api but in only is: https://sandbox.api.visa.com/cybersource/payments/flex/v1/keys?apikey={apikey} No exists v2.
... View more
June
1 Kudo
Thanks for your prompt response, in effect, I'm using v1 so I'll make the change. I will be alerting here the progress you have.
... View more
June
1 Kudo
Hi! Then, I tryed the encryption type of “None” and the answer is: "status": 504, "data"=> [] Them, I tryed the encryption type of “None” and the anser is: "status": 403, "reason": "TOKENIZATION_ERROR", "message": "Tokenization provider error: Recurring Billing or Secure Storage service is not enabled for the merchant" So, my questions are: if I can use Flexible Token API of sandbox? or only work in production environment? In this case, what mean code 504? I can setup my user Merchant of test (cyttek_consor_30897_acc) to make this test? Thanks in advance,
... View more
Public Statistics
| Date Registered | May 2018 |
| Date Last Visited | |
| Total Messages Posted | 11 |
| Total Kudos Received | 4 |
Latest Tags
No tags yet