The CvvOperations section allows you to manage all aspects of collecting the CVV of a card from the card owner and process a charge on the card using your preferred payment processor.
With the CvvOperations, you can design your own payment flow based on your needs and specifications. You can perform the CvvOperations either in our default form or you can design your own form(s) to perform the CVV operations there. Additionally, if you would like, you can store your forms in Orchestra and embed them into your website (this can help take you out of PCI compliance scope).
Adding custom forms can be achieved either from our portal or via our API.
We assume that your web application will submit all CvvOperations from the client. However, since the data sent from the client - either to our API or back to your server, can be compromise, we have designed an authentication process that will serve to both pass data between your server and our API - via the client, and to authenticate the request itself.
For the first step, you will need to start the CVV Operations session by using [POST] /CvvOperations. This method will allow your server to specify to the API which operations are permitted within this CvvOperations session and provide all parameters that the client should not be able to manipulate (for example, value of the transaction).
The response to this method would be a JWS authentication token which will be used in all subsequent requests within the CardOperations process.
Mixed Authentication Mechanisms
The methods in the CardOperations utilize two forms of authentication.
[POST] /CardOperationsmethod, to start a CardOperations session, uses your API key as authentication. The result of which is an authentication code.
- The other methods under CardOperations all use bearer token authentication (the bearer token is the authentication code returned in the response to the initial
Once you received the AuthToken for this CardOperations session, you can then submit any of the CardOperations methods to perform any of the following actions on the card:
- Perform card validation
- Perform 3D Secure Authentication
- Perform Universal payment gateway charge operation
- Tokenize and store card number
In each of these methods, you will need to provide the specific details necessary to complete this operation (keep in mind that some, and perhaps even all) of the data necessary for this operation has already been provided as part of the process of creating the session.
The response of each of these methods will include both the specific result of the operation performed and an updated JWS AuthToken which should be used as the bearer authentication token of the next request.
You can perform these actions in any order that suits your needs and your workflow, and you can run them as many times as needed. You can design either the client app or the server app (we would recommend the server app) to define the conditions and the logic of when and following what result to proceed to the next step (for example, you might not want to process a charge on a card that failed 3D Secure authentication or you would not want to store a card that the charge was rejected due to invalid card).
In addition to the CardOperations methods, we also offer a method to validate the AuthToken which allows you to confirm the responses your server receives from the client.