Description
The chargeTokenCreditCard request will charge a transaction created by createToken
URL: https://secure1.sandbox.directpay.online/API/v6/
Response
The method will response with the result of your request
Variables to send:
Parameter | Data type | Description | |
Request | Text | chargeTokenCreditCard | Mandatory |
CompanyToken | Token | Token you got from 3G to operate this API | Mandatory |
TransactionToken | Token | Transaction token as accepted from the createToken. | Mandatory |
CreditCardNumber | Number | Credit card number | Mandatory |
CreditCardExpiry | MMYY | Month and year of expiry of credit card | Mandatory |
CreditCardCVV | Number | 3-4 digits of CVV | Mandatory |
CardHolderName | Text | Card holder name | Mandatory |
ChargeType | Text | Charge type of the card | Optional |
ThreeD | Data | Data for 3D process | Optional |
ThreeD data to send (Data for 3D process (depend by terminal (MPGS3D, MPGS3DAirlines, MIGS3D, PG3D))):
Parameter | Data type | Description | |
Enrolled | Text | 3D param, mandatory for PG3D, MIGS3D | Optional |
Paresstatus | Text | 3D param, mandatory for PG3D, MIGS3D(vpc_3DSstatus) | Optional |
Eci | Text | 3D param, mandatory for all terminal types | Optional |
Xid | Text | 3D param, mandatory for all terminal types | Optional |
Cavv | Text | 3D param, mandatory for all terminal types | Optional |
Signature | Text | 3D param, mandatory for PG3D | Optional |
Veres | Text | 3D param, mandatory for MPGS3D, MPGS3DAirlines, MIGS3D | Optional |
Pares | Text | 3D param, mandatory for MPGS3D, MPGS3DAirlines | Optional |
Request example:
<?xml version="1.0" encoding="utf-8"?> <API3G> <CompanyToken>57466282-EBD7-4ED5-B699-8659330A6996</CompanyToken> <Request>chargeTokenCreditCard</Request> <TransactionToken>72983CAC-5DB1-4C7F-BD88-352066B71592</TransactionToken> <CreditCardNumber>123412341234</CreditCardNumber> <CreditCardExpiry>1214</CreditCardExpiry> <CreditCardCVV>333</CreditCardCVV> <CardHolderName>John Doe</CardHolderName> <ChargeType></ChargeType> <ThreeD> <Enrolled>Y</Enrolled> <Paresstatus>Y</Paresstatus> <Eci>05</Eci> <Xid>DYYVcrwnujRMnHDy1wlP1Ggz8w0=</Xid> <Cavv>mHyn+7YFi1EUAREAAAAvNUe6Hv8=</Cavv> <Signature>_</Signature> <Veres>AUTHENTICATION_SUCCESSFUL</Veres> <Pares>eAHNV1mzokgW/isVPY9GFSCL0EEZkeyg7</Pares> </ThreeD> </API3G>
Respond:
The server will respond for the chargeTokenCreditCard request according to the following results:
Parameter | Data type | Description |
Result | 3/4 digits code | A code will be sent with the result of the request |
ResultExplanation | Text | Free text of the result |
Respond codes:
Code | Explanation |
000 | Transaction charged |
200 | Transaction already paid |
801 | Request missing company token |
802 | Wrong CompanyToken |
803 | No request or error in Request type name |
804 | Error in XML |
902 | Data mismatch in one of the fields – fieldname |
950 | Request missing mandatory fields – fieldname |
999 | Transaction Declined - Explanation |
Respond example:
<?xml version="1.0" encoding="utf-8"?> <API3G> <Result>000</Result> <ResultExplanation>Transaction charged </ResultExplanation> </API3G>