Skip to main content

Transactions Supported

The axept® GO application supports the following transaction types.

Sale​

To request that axept® GO performs a sale/purchase the below request is required.

EFTServiceLib.runTrans
(
    this, 
    <TransactionValueInPence>, 
    TRANSACTION_TYPE_SALE, 
    "<MerchantDepartmentId>",
    "<UserId>",
    "<Password>", 
    "<ReferenceNumber>"
);

An example request is shown below:

EFTServiceLib.runTrans(this, 100, TRANSACTION_TYPE_SALE, "4122", "1234", "1234", "TESTSALEREF");

The MerchantDepartmentId, UserId, Password and ReferenceNumber fields are optional.

Refund​

To request that axept® GO performs a refund the below request is required.

EFTServiceLib.runTrans
(
    this, 
    <TransactionValueInPence>, 
    TRANSACTION_TYPE_REFUND, 
    "<MerchantDepartmentId>",
    "<UserId>",
    "<Password>", 
    "<ReferenceNumber>"
);

An example request is shown below:

EFTServiceLib.runTrans(this, 100, TRANSACTION_TYPE_REFUND, "4122", "1234", "1234", "TESTSALEREF");

The MerchantDepartmentId, UserId, Password and ReferenceNumber fields are optional.

Sale with Gratuity​

axept® GO allows the integrated app to pass the gratuity value in the transaction request for sales. This is optional, and axept® GO can instead manage the capturing of the gratuity value if required.

EFTServiceLib.runTrans
(
    this,
    <TransactionValueInPence>,
    <GratuityValueInPence>,
    TRANSACTION_TYPE_SALE,
    "<MerchantDepartmentId>",
    "<UserId>",
    "<Password>",
    "<ReferenceNumber>"
);

An example request is shown below:

EFTServiceLib.runTrans(this, 100, 1000, TRANSACTION_TYPE_SALE, "4122", "1234", "1234", "TESTREF");

The MerchantDepartmentId, UserId, Password and ReferenceNumber fields are optional.

Cardholder Not Present (CNP) Sale​

To request that axept® GO performs a CNP sale the below request is required.

EFTServiceLib.runTrans
(
    this, 
    <TransactionValueInPence>, 
    TRANSACTION_TYPE_CNPSALE, 
    "<MerchantDepartmentId>",
    "<UserId>",
    "<Password>", 
    "<ReferenceNumber>"
);

An example request is shown below:

EFTServiceLib.runTrans(this, 100, TRANSACTION_TYPE_CNPSALE, "4122", "1234", "1234", "TESTREF");

The MerchantDepartmentId, UserId, Password and ReferenceNumber fields are optional.

Cardholder Not Present (CNP) Refund​

EFTServiceLib.runTrans
(
    this, 
    <TransactionValueInPence>, 
    TRANSACTION_TYPE_CNPREFUND, 
    "<MerchantDepartmentId>",
    "<UserId>",
    "<Password>", 
    "<ReferenceNumber>"
);

An example request is shown below:

EFTServiceLib.runTrans(this, 100, TRANSACTION_TYPE_CNPREFUND, "4122", "1234", "1234", "TESTREF");

The MerchantDepartmentId, UserId, Password and ReferenceNumber fields are optional.

Reference Field and Data Security​

Personally Identifiable Information

In the ReferenceNumber fields above, you are free to pass a wide variety of data. You must however be careful to not include any Personally Identifiable Information. This can include vehicle registration details, cardholder name, and many other data. Please refer to European General Data Protection Regulations (Article 4) for detailed guidance on what should not be included here.

Reversals​

axept® GO does NOT currently support integrated elective Reversals. Reversals required in the processing of a transaction, such as the reversal of a signature verification failure, are performed automatically.

If a reversal is attempted via integration to axept® GO a response will be sent back and will populate the below fields as “false”. See Unsupported Transaction Types for more detail.

  • Approved
  • TransResponse
  • TransactionDetails

Query Transaction​

axept® GO allows the integrated application to query the result of a transaction based upon the “Unique Transaction Identifier” value returned.

EFTServiceLib.queryTrans(this, lastReceivedUTI)

An example request is shown below:

EFTServiceLib.queryTrans(this, TEST123);