On This Page
Simple Order API
Validation Service Request
When you make the validation request, you must:
- Extract the PARes message from the form received from the card-issuing bank.
- Remove any spaces created by tabs, spaces, or line breaks from thePaResfield. Do not modify any other part of thePaResfield.
- Send thePaResvalue toCybersourcein the signedPaResfield of the validation service. The response contains the validation result.
You can use the validation and card authorization services in the same
request or in separate requests:
- Same request—Cybersourceautomatically attempts to authorize your customer’s card if validation succeeds. The values of the required fields are added automatically to the authorization service. Do not pass any fields thatCybersourcederives from thePaResvalue into the request because that data could be overwritten.
- Separate requests—You must manually include the validation result values (Payer Authentication response fields) in the authorization service request (Card Authorization request fields), which are listed in this table:
Identifier | Payer Authentication Response Field | Card Authorization Request Field |
---|---|---|
XID | payerAuthValidateReply_xid | ccAuthService_xid |
E-commerce indicator | payerAuthValidateReply_commerceIndicator
| ccAuthService_commerceIndicator
|
CAVV | PayerAuthValidateReply_cavv | ccAuthService_cavv |
If you are currently passing additional card-specific values in the Payer
Authentication Validate response for Visa and Mastercard, you can continue to pass
them for RuPay.