chargeTokenAuth (V6)
Description
The chargeTokenAuth request will charge a transaction created by createToken and which was authorized
URL:Â https://secure.3gdirectpay.com/API/v6/
Â
Response
The method will response with the result of your request
Variables to send:
Parameter | Data type | Description | |
 Request |  Text |  chargeTokenAuth | Mandatory |
CompanyToken | Token | Token you got from 3G to operate this API | Mandatory |
TransactionToken | Token | Transaction token as accepted from the createToken. | Mandatory |
Request example:
<?xml version="1.0" encoding="utf-8"?> <API3G> <CompanyToken>57466282-EBD7-4ED5-B699-8659330A6996</CompanyToken> <Request>chargeTokenAuth</Request> <TransactionToken>72983CAC-5DB1-4C7F-BD88-352066B71592</TransactionToken> </API3G>
Respond:
The server will respond for the chargeTokenAuth request according to the following results:
Parameter | Data type | Description |
Result | 3 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 queued for charge - The transaction is now on the queue for charge by our automated procedures |
800 | Transaction not authorized - The transaction was not yet authorized, it needs to be authorized by the customer manually using the payment page or by the chargeTokenCreditCard request |
801 | Request missing company token |
802 | Company token does not exist |
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 |
903 | Transaction not found |
905 | Transaction already charged |
Respond example:
<?xml version="1.0" encoding="utf-8"?> <API3G> <Result>000</Result> <ResultExplanation>Transaction queued for charge</ResultExplanation> </API3G>