Transaction

Call this method to provide Dynamic currency conversion (DCC) inquiry details for your customer

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/DccInquiry
200Success

Call this method to get information about a previously initialized alternative payment transaction

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/QueryAlternativePayment
200Success

This method can be used to authorize the payments that do not have a payment-page or for the payments that before authorization some additional steps such as authentication should be done.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/AlternativePayment
200Success

This method can be used to get the details of a transaction that has been authorized successfully. Fair use:This method is not intended for polling. You have to restrict the usage of this method in order to provide a fair data access to all our customers. We may contact you if we notice the excessive usage of this function and in some exceptional cases we preserve the right to limit the access to it.

post

ATTENTION: If you change the name of this method, make sure that the value of the field ActionIdOfCallToTransactionInquire in AnalyzerLogRepository is updated as well.

Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/Inquire
200Success

WARNING: This feature is deprecated and replaced by the Payment Page. Please use the parameter PaymentMethods to directly select the desired 3rd party provider!

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/AssertRedirectPayment
200Success

WARNING: This feature is deprecated and replaced by the Payment Page. Please use the parameter PaymentMethods to directly select the desired 3rd party provider!

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/RedirectPayment
200Success

This method may be used to cancel previously authorized transactions and refunds.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/Cancel
200Success

This method may be called to refund an amount to the given means of payment (not supported for all means of payment) without referencing a previous transaction. This might be the case if the original transaction was done with a card which is not valid any more. Warning: Only PCI certified merchants may submit the card-data directly, or use their own HTML form! Click here for more information!

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/RefundDirect
200Success

This method may be used to inquire the status and further information of pending refunds. Attention: This method is only supported for pending refunds. A pending refund is only applicable for paydirekt or WL Crypto Payments transactions at the moment.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/AssertRefund
200Success

This method may be called to refund a previous transaction.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/Refund
200Success

This method may be used to finalize a transaction having one or more partial captures (i.e. marks the end of partial captures).

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/MultipartFinalize
200Success

Attention: This method is only supported for pending captures. A pending capture is only applicable for PostFinance Instant Payout transactions at the moment. This method is only supported for pending capture transactions (only used for PostFinance Instant Payout at the moment)

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/AssertCapture
200Success

This method may be used to capture multiple parts of an authorized transaction. Important: MultipartCapture is available for PayPal, Klarna and card payments Visa, Mastercard, Maestro, Diners/Discover, JCB and American Express which are acquired by Worldline. No MultipartCapture request should be sent before receiving the response of a preceding request (i.e. no parallel calls are allowed). The sum of multipart captures must not exceed the authorized amount. A unique OrderPartId must be used for each request.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/MultipartCapture
200Success

This method may be used to finalize previously authorized transactions and refunds.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/Capture
200Success

This method may be used to perform follow-up authorizations to an earlier transaction. At this time, the referenced (initial) transaction must have been performed setting either the recurring or installment option.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/AuthorizeReferenced
200Success

This function may be used to directly authorize transactions which do not require a redirect of the customer (e.g. direct debit or recurring transactions based on a previously registered alias). Warning: Only PCI certified merchants may submit the card-data directly, or use their own HTML form! Click here for more information! Important: This function does not perform 3D Secure! Only the PaymentPage or Transaction Initialize do support 3D Secure!

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/AuthorizeDirect
200Success

This function may be called to authorize a transaction which was started by a call to Transaction/Initialize.

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/Authorize
200Success

This method may be used to start a transaction which may involve either DCC and / or 3d-secure. Warning: Only PCI certified merchants may submit the card-data directly, or use their own HTML form! Click here for more information!

post
Authorizations
AuthorizationstringRequired

Basic authentication with your Saferpay API user credentials.

Body
Responses
chevron-right
200Success
application/json
Responseone of | nullable
post
/Payment/v1/Transaction/Initialize
200Success

Last updated

Was this helpful?