Visa Developer Community

I spent a while looking for documentation for sending a tokenized payment authorization request to the CyberSource payments REST API. The documentation shows all possible request bindings, but I was unable to format a sandbox request which would allow me to authorize a card using the payment token rather than the card number. No matter what I would do, I got this result:   "errorInformation" : { "reason" : "INVALID_ACCOUNT", "message" : "Decline - Invalid account number" }, Note that generating a payment profile seems to work fine. I understand that there is a team specifically for handling CyberSource related questions, so I called them, but I was told that the API is in beta, some of the documentation might be missing, and that they were unable to help me. However, it sounded like it should be possible to get the request to succeed, just that there isn't complete documentation for doing so. They also mentioned a "subscriptionID" binding, but I don't see this anywhere in the documentation.   Given that the CyberSource help line wasn't able to answer my question and there is no documentation for this specific case, I understand that I may not get an answer here, but just in case, does anyone happen to know how to authorize a card this way? Again, I want to send an authorize request to the API I linked without using the card number, so the example code which uses the card number won't work for my use case.   Edit: Looking at my request bindings, paymentInformation > customer > customerId seems like it could be the "invalid account number" the response is referring to. However, I don't see any other binding in the request or response for tokenizing the card that would represent this account number, so it seems like I should just be using the payment profile ID or subscription ID. ... View more

I was looking over this documentation on processing a payment and looking over the "capture" and "authType" bindings. I'm trying to set up the request so it will both auth and capture, then send a response that indicates whether it authed and captured. I'm not concerned with partial captures, so can I do the following?   Set "capture" to true and "authType" to "AUTOCAPTURE" in the request bindings If the response says the transaction was successful, assume that the customer was charged for the amount in the "authorizedAmount" binding of the response If the response says the transaciton was unsuccessful, assume that the customer was not charged I would prefer not to have to send a second request to the "capture" endpoint in cases where I want to capture immediately, since this workflow would be simpler. However, I want to make sure I can safely assume that the customer was charged the "authorized" amount in successful cases and not charged at all in unsuccesful cases. ... View more

Sorry if this has already been covered in another thread, but I wasn't able to find an answer when I looked. I'm currently working in a sandbox environment and it looks like I can successfully generate FlexPublicKeys and payment profiles. I want to make sure I also set up a workflow for checking for existing keys/profiles before trying to generate them, as well as updating existing payment profiles.   I noticed that FlexPublicKey in the CyberSource Flex SDK has a method called "retrieveKey()" which sounds like what I should be using. Specifically, I'm thinking of calling this method when I need a FlexPublicKey for a request, and calling generateKey() if the result is null. Is this an intended/workable use case? What is the String argument that retrieveKey() takes?   For payment profiles, I've been working based off example code from this repo and making the request to generate a payment profile using VisaClient.doXPayTokenRequest(). From what I can tell, the identifier that specifies that the request is meant to generate a profile is "tokens" in the resource path, and the endpoint generates a payment profile based on values in the request body and includes the profile id in the response body. Is there a type of request that simply checks whether a profile exists and another that updates an existing profile? Or should I just use the same workflow for both of these cases as for generating a new profile, and build the application in such a way that it doesn't care whether a payment profile exists and always attempts to "generate" one?   ... View more