×
Menu

Capita Payment Integration

 
This page details the inputs, secure inputs and outputs available for the Capita Logic Item, how to complete each field, and an external link to the Capita integration documentation.
 
PCI Pal must check any payment gateway integrations prior to going live.  The documentation disclaimer (which applies throughout this guide) should be read before commencing any configuration of payment gateways.
 

Inputs

 
Input Fields
Required
Character Limits/
Required Input
Description
hmacKey
Yes
Unique to the client
Client specific HMAC key to encrypt the request
kid
Yes
Unique to the transaction
HMAC Ke6y ID, provided by Capita Pay360
iAt
Yes
10 numbers
‘issued at’ UTC Date/Time formatted as the number of seconds since 01/01/1970 00:00:00
callId
Yes
Call specific
PCI Pal Call ID
phoneNumber
No
Phone number specific
Callers phone number
uniqueTranId
Yes
60 chars
Unique transaction id
 
Secure Inputs
Input Fields
Required
Character Limits/
Required Input
Description
cardNumber
Yes
19 chars
Secure input of the card number
cardExpiryDate
Yes
4 chars
Secure input of the card expiry - in the format MMYY
cardSecurityCode
Yes
3 or 4 chars
Secure input of the card CVV, either three or four digits long depending on the card
 
Outputs
Output Fields
Description
uniqueTranIdResult
Unique ID of the transaction provided in the request
iat
Time the response is issued at
statusCode
Numeric status code which relates to the result of the payment, the values are the following:
0 - Success
2 - Card details already stored
8 - Unique Tran ID not registered
9 - Service Under Construction
10 - Invalid header
11 - Invalid signature
12 - Invalid payload
13 - Invalid card details
14 - Invalid request
90 - System Error
statusCodeDescription
The description of the status code
errorMessage
PCI Pal specific error message.  If anything goes wrong in the sending of a request, our internal error handling will respond with a message on the output of the flow
 
Capita Logic Item
The Capita Logic Item contains the following properties:
 
Capita Payment Integration
1

HMAC Key

Client specific HMAC key to encrypt the request.
2

Success Code

Each gateway has its own unique selection of status codes on a request back from the gateway - for CyberSource, these are:
0 - Success
2 - Card details already stored
8 - Unique Tran ID not registered
9 - Service Under Construction
10 - Invalid header
11 - Invalid signature
12 - Invalid payload
13 - Invalid card details
14 - Invalid request
90 - System Error
 
This must be set in order for our internal logging processes to notice that the payment has come back with the expected response.
3

Select Endpoint

  For added security the CyberSource endpoints have been hardcoded into the integration.  Test or Live needs to be selected from the Select Endpoint drop down list, depending on the transaction being conducted.
Further information can be found by viewing the integration documentation:
 
The help manual was created with Dr.Explain