Update a payment and continue processing

patch

https://prod.emea.api.fiservapps.com/sandbox/ipp/payments-gateway/v2/payments/{transaction-id}

Use this to handle a redirect response, updating the transaction and continuing processing.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

transaction-id

string

required

Gateway transaction identifier as returned in the parameter ipgTransactionId or merchantTransactionId. In case you want to use the merchantTransactionId to query the transaction status use this format: .../payments/merchantTransactionId= This is applicable for other scenarios as well, such as void, refund or other secondary transactions.

Body Params

Accepted request types: Secure3DInitiateRequest, Secure3DAuthenticationUpdateRequest, Secure3D10AuthenticationUpdateRequest and Secure3D21AuthenticationUpdateRequest.

Provides shared fields for all AuthenticationUpdateRequest types. Abstract class, do not use this class directly, use one of its children.

storeId

string

length ≤ 20

An optional Outlet ID for clients that support multiple stores in the same developer app.

authenticationType

string

required

Object name of the authentication update request.

billingAddress

object

Address information that is passed to the issuer (it may appear on the cardholder’s statement) or if merchant wants to pass information that differs from the information stored on our master file.

authenticationRequest

object

required

Request authentication of the payment card to verify the cardholder and be eligible for liability shift. An AuthenticationRequest should not be submitted with in the same request as an AuthenticationResult. Abstract class, do not use this class directly, use one of its children.

Headers

Content-Type

string

enum

required

Defaults to application/json

Content type.

Allowed:

Client-Request-Id

string

required

A client-generated ID for request tracking and signature creation, unique per request. This is also used for idempotency control. We recommend 128-bit UUID format.

Api-Key

string

required

Key given to merchant after boarding associating their requests with the appropriate app in Apigee.

Timestamp

int64

required

Epoch timestamp in milliseconds in the request from a client system. Used for Message Signature generation and time limit (5 mins).

Message-Signature

string

required

Used to ensure the request has not been tampered with during transmission. The Message-Signature is the Base64 encoded HMAC hash (SHA256 algorithm with the API Secret as the key.) For more information, refer to the supporting documentation on the Developer Portal.

Responses

200Success response.

400The request cannot be validated.

401The request cannot be authenticated or was submitted with the wrong credentials.

403The request was unauthorized.

404The requested resource doesn't exist.

409The attempted action is not valid according to gateway rules. For example, the merchant is not set-up or the order already exists.

415Format that is not supported by the server for the HTTP method.

422The processor declined the transaction.

500An unexpected internal server error occurred.

502There was a problem communicating with the endpoint.

API Products

Point of Sale

Developer

Resources