Selecting a currency
Learn how to determine whether a currency is supported and how it is prioritized.
Last updated
Learn how to determine whether a currency is supported and how it is prioritized.
Last updated
require a currency that conforms to the standard.
However, not all currencies in the ISO 4217 list are supported in the Digital River APIs. Instead, the currency you pass must be used to fund the transaction.
You should also remember that the currency you send in a or always over the value you pass when .
Refer to the to access a list of available currencies for each .
If the currency you send in a request that is not supported by the , you receive the following error:
You might also receive a 409 Conflict response that contains a code of invalid_parameter. In this case, the error could have been thrown because currency consisted of incorrect characters, an obsolete, Euro-zone currency, or another currency no longer circulated.
For some payment methods, it's required that you set currency in the configuration object of , while for others, it's optional.
However, if you do pass currency, and then , the currency doesn't need to match the currency. Both values just have to be .
The currency always takes priority over the currency. This means upon creation, we generate a charge in the currency.
The following example demonstrates this concept. In this case, a payment source in USD is with a currency of HKD. After the , the payment.charges[].currency is also HKD.