Backend Operations

Transaction-Based Operations

Transaction-based operations depend on existing orders, which have been completed by your online shop consumer.

Table 1. Available Transaction-Based Operations
Operations	Description
`approveReversal`	Cancel an approval, typically done by your consumer in your online shop.
`deposit`	Convert an approval into a deposit.
`depositReversal`	Cancel a deposit.
`getOrderDetails`	Return all order details including corresponding payments and credit notes.
`recurPayment`	Create a new order based on an existing order, typically used for subscriptions.
`refund`	Create a credit note for an order, typically done by the merchant after the consumer returned an ordered product.
`refundReversal`	Cancel a credit note.
`transferFund`	Create a credit note without dependency on an pre-existing payment.

Availability of a transaction-based operation depends on:

You can always get all currently available transaction-based operations of a specific order by using the operation getOrderDetails.

You can find a detailed table displaying all supported payment methods and their corresponding transaction-based operations at transaction-based operations by payment method.

Non-transaction-based operations don’t depend on existing orders and are carried out independently of any existing orders.

Table 2. Available Non-Transaction-Based Operations
Operation	Description
`generateOrderNumber`	Create a new order number in the payment system.
`getFinancialInstitutions`	Querying possible and supported financial institutions of a certain payment method.

Availability of a non-transaction-based operation depends on: