Learn how to determine whether a currency is supported and how it is prioritized.
Checkouts require a currency that conforms to the ISO 4217 standard.
However, not all currencies in the ISO 4217 list are supported in the Digital River APIs. Instead, the currency you pass must be supported by the payment method used to fund the transaction.
If the currency you send in a create or update checkout request that is not supported by the source, you receive the following error:
{"type": "conflict","errors": [ {"code":"currency_unactivated","parameter":"currency","message":"Currency 'PAB' is not activated." } ]}
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.
{"type": "bad_request","errors": [ {"code":"invalid_parameter","parameter":"currency","message":"'YEM' is not a valid currency." } ]}
How currency is prioritized
For some payment methods, it's required that you set currency in the configuration object of createSource(), while for others, it's optional.
The checkout's currency always takes priority over the source'scurrency. This means upon order creation, we generate a charge in the checkout's currency.