Menu

User Tools

Create PDF

Site Tools


This is an old revision of the document!


Core Feature Comparison in Detail

JAPI/SAPI

Java API/Serial API are the Java software library and the interface for the QTill Server.

Feature Description
Initiate Payment Mandatory parameters:
  • inittype (to initialize a specific payment method)
  • amount
  • currency
  • orderNumber
  • orderDescription
3-D Secure:
  • Specific inittype (3DSECURE) which implicitly checks for 3-D Secure enrollment.
  • If card is enrolled, merchant needs to send verifyPayment with additional 3-D Secure data received from ACS redirect.
Verify payment Follow up of initiatePayment. Checks payment status of a single payment.

Mandatory parameter:
orderNumber (which has been returned on initiatePayment)

Result:
  • Success returns payment details
  • Error
Deposit Transfer of authorization into deposit (capture).

Mandatory parameters:
  • orderNumber (returned on initiatePayment)
  • paymentNumber (= orderNumber)
  • amount (amount to be deposited)
Recurring Payment Creates new order and payment based on already existing order.

Mandatory parameters:
  • orderNumber (new number from createOrder)
  • sourceOrderNumber (parent transaction)
  • amount
  • currency
  • orderDescription
Refund Creates refund for already closed deposit. Only possible if deposit and closing for order are already completed.

Mandatory parameters:
  • orderNumber (orderNumber of order which is to be refunded)
  • amount
Query queryOrders:
Returns information about all orders and their payment and refund status for given input parameters.

Mandatory parameter:
“For” to specify which orders to return (depending on status).

queryCredits:
Returns all refunds.

queryBatches:
Returns information about daily batches - either closed or open (depending on request parameters).
Approve reversal Reverses an authorization for a payment which has not yet been deposited.
Deposit reversal Reverses a deposit if daily closing has not yet been done.

Toolkit

Click here for comprehensive Toolkit documentation.

Feature Description
Initiate payment Triggered by
  • WCS or WCP
  • JAPI/Serial API direct call
Verify payment queryOrders with orderNumber as primary key
Deposit Transfer of authorization into deposit (capture).

Mandatory parameters:
  • orderNumber (returned on initiatePayment)
  • paymentNumber (usually equal to orderNumber)
  • amount (amount to be deposited)
Recurring payment Available as add-on. Creates new order and payment based on already existing order.

Mandatory parameters:
  • orderNumber (new number from createOrder)
  • sourceOrderNumber (parenttransaction)
  • amount
  • currency
  • orderDescription
Refund Creates refund for already closed deposit. Only possible if deposit and closing for order are already completed.

Mandatory parameters:
  • orderNumber of order which is to be refunded
  • amount
Query queryOrders:
Returns information about all orders and their payment and refund status for given input parameters.

Mandatory parameter:
“For” to specify which orders to return (depending on status).

queryCredits:
Returns all refunds.

queryBatches:
Returns information about daily batches - either closed or open (depending on request parameters).
Approve reversal Reverses an authorization for a payment which has not yet been deposited.
Deposit reversal Reverses a deposit if daily closing has not yet been done.

Toolkit light

Toolkit light documentation:

Feature Description
Initiate payment Triggered in front-end by WCS or WCP
Verify payment Return all details for a given order:
  • WCP command: getOrderDetails
  • WCS endpoint: /seamless/backend/getOrderDetails
Deposit Approval converted into capture:
  • WCP command: deposit
  • WCS endpoint: /seamless/backend/deposit
Recurring payment Create payment by reusing information from previous order:
  • WCP command: recurPayment
  • WCS endpoint: /seamless/backend/recurPayment
Refund Refund already closed order:
  • WCP command: refund
  • WCS endpoint: /seamless/backend/refund
Query Not possible to query multiple orders; possible to get single order details by order number:
  • WCP command:getOrderDetails
  • WCS endpoint: /seamless/backend/getOrderDetails
Approve reversal Cancel of approval:
  • WCP command: approveReversal
  • WCS endpoint: /seamless/backend/approveReversal
Deposit reversal Cancel of deposit:
  • WCP command:depositReversal
  • WCS endpoint: /seamless/backend/depositReversal

Wirecard PHP Payment SDK

Detailed documentation, examples and download: https://github.com/wirecard/paymentSDK-php/

Feature Description
Initiate payment Operational functions:
  • credit card UI for input fields generated via seamless Payment Page
  • pay(): initiates payment process or captures authorization
  • reserve(): authorization request
3-D Secure:
  • credentials for 3-D Secure added in configuration
  • limits added in configuration
  • reserve() and pay() functions check enrollment and redirect to 3-D Secure authentication if 3-D Secure is possible
Verify payment
  • replaced by notification handling server-to-server request regarding changes in status
  • server notification received after payment has been completed successfully
Deposit pay() function:
  • initiates payment process or
  • captures an existing authorization (reserve())
Recurring payment A recurring payment is based on a previous transaction, which returns tokenID as response if the transaction was successful. It is performed with the function pay(), using the additional parameter tokenID.

Recurring payments are available for:
  • Credit Card
  • Maestro SecureCode
  • SEPA Direct Debit
Refund There are two different refund functions:
  • cancel(): requests to void a transaction. If voiding is no longer possible, a refund is initiated.
  • credit(): performs a pay() in the opposite direction (pays a specific amount to the consumer).
Query You can query transactions by:
  • transaction-id: returns single transaction
  • parent-transaction-id: returns all corresponding transactions
See sample source: transaction.php
Approve reversal cancel(): If a payment has been authorized but not yet captured, cancel() leads to a void of authorization.
Deposit reversal cancel(): If a credit card payment has already been captured, cancel() leads to a refund.

REST API

Comprehensive documentation:

Feature Description
Initiate payment Transaction types:
  • preauthorization
  • authorization
  • authorization-only
  • final-authorization
  • authorization-supplementary
  • get-url
  • debit
  • purchase
3-D Secure:
  • Check enrollment
  • Customer ACS Communication
  • Check Payers Response
  • Payment Request
Verify payment General API request to get status of asynchronous payment
Example: here for an example.
Deposit Transaction types:
  • capture-authorization (to take funds from the card holder after authorization)
  • capture-preauthorization
  • capture-final-auth
  • deposit
Recurring payment Transaction types:
  • debit
  • authorization
  • referenced-purchase
  • referenced-authorization
Additional elements in XML request:
  • periodic
  • periodic-type
  • sequence-type
Recurring based on
  • merchant-tokenization-flag and tokenID
  • parent-transaction-id
Refund Transaction types:
  • refund-capture (moves funds back to cardholder according to a corresponding capture)
  • refund-purchase (returns funds based on purchase)
  • refund-request & refund-debit
  • chargebacks: first-cb, second-cb
Query Single queries are possible via REST API based on:
  • transaction-id
  • request-id
  • request-idandcategory
  • group-transaction-id
Approve reversal Transaction types:
  • void-authorization
  • void-preauthorization
  • void-final-authorization
  • void-auth-supplementary
  • void-debit
  • reversal-authorization
Deposit reversal Transaction types:
  • void-capture
  • void-debit
  • void-purchase
  • reversal-purchase
  • void-capture-preauthorization
  • void-capture-final-auth

This website uses cookies to deliver the best service to you. By continuing to browse the site, you are agreeing to our use of cookies.