Generate dynamic currency conversion transactions

post

https://prod.emea.api.fiservapps.com/sandbox/ipp/payments-gateway/v2/exchange-rates

Sale, return and lookup exchange rate with dynamic currency conversion option

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Accepted request types: DCCExchangeRateRequest and DynamicPricingExchangeRateRequest.

Request to perform an exchange rate inquiry. Abstract class, do not use this class directly, use one of its children.

requestType

string

required

Object name of the exchange rate request.

baseAmount

number

required

The original amount of the merchant currency for calculation.

storeId

string

length ≤ 20

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

bin

string

required

The bank identification number (BIN) of the card to be used for DCC. The BIN is the first 6-11 digits of the card number.

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

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

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.

500An unexpected internal server error occurred.

502There was a problem communicating with the endpoint.

API Products

Point of Sale

Developer

Resources