Alternative Payment Methods
Klarna
Key Differences Between Steps
Affirm
Vipps
A value you specify that uniquely identifies this transaction. This must be used to trigger a reversal if there is a timeout.
63bbc548-d2de-4546-b106-880a5018461cThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711The Phone Number registered with Vipps Mobile APP.
+31-6-11223344Checkout Redirect URL which will be used by Vipps on Payment Completion.
Flag to identify the transaction originated from APP or Browser.
falseExample: falseAmount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
150Flags a payment request for either pre-authorization or final authorization.
PRE_AUTHis used when the authorized amount is unknown and can be adjusted later.FINAL_AUTHis used when a final authorized amount is known and the transaction will definitely be captured in whole.
FINAL_AUTHPossible values: Whether auto-capture or not. Setting the value to 'false' will only authorize the transaction.
trueExample: falseThe ID of a customer.
0a57b387-2ba7-4f65-be2f-e176bb49d2ceThe IP Address of the customer where the transaction was initiated.
127.0.0.1A short descriptor to be shown on bank statement of the customer. Please refer to the integration guide for the format requirements.
A reference specified by the merchant to identify the transaction.
7a1db7a8-6f24-4bc5-a51b-cef33fc05140The full user agent string of the device the customer used to submit the transaction.
A reference used by the merchant to typically capture a description of the service provided. It could then be used by the merchant to help locate transactions. One could envision a situation where a merchant is trying to locate a transaction/ receipt but in speaking with the customer, the only (or at least a predominant) detail is what service was rendered
Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to ISO 4217.
Please note that Klarna only supports Norwegian krone (NOK).
NONE: No SCA required.WALLET: Depend on the wallet SCA mechanism. For Google Pay this means that MasterCard will shift liability, Visa will not.FORCE_3DS: Do an additional 3DS step regardless of whether the wallet indicates the token is SCA-compliant.
WALLETPossible values: Use this field to request your transaction to be exempted from the application of the Strong Customer Authentication (SCA). Be advised that the use of this field may result to your liability in case of fraudulent transaction. Possible Values: 1 - Low value payment 2 - Acquirer Transaction Risk Analysis 3 - Trusted beneficiary exemption 4 - Secure Corporate Payment (SCP) exemption 5 - Merchant Initiated Transaction 6 - SCA Delegation.
NOTE: This only applies when sca_compliance_level = NONE
The Vipps Payment Initiation Response.
Bad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
MobilePay
A value you specify that uniquely identifies this transaction. This must be used to trigger a reversal if there is a timeout.
63bbc548-d2de-4546-b106-880a5018461cThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711Checkout Redirect URL which will be used by MobilePay on Payment Completion.
Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
0Flags a payment request for either pre-authorization or final authorization.
PRE_AUTHis used when the authorized amount is unknown and can be adjusted later.FINAL_AUTHis used when a final authorized amount is known and the transaction will definitely be captured in whole.
FINAL_AUTHPossible values: Whether auto-capture or not. Setting the value to 'false' will only authorize the transaction.
trueExample: falseThe ID of a customer.
0a57b387-2ba7-4f65-be2f-e176bb49d2ceThe IP Address of the customer where the transaction was initiated.
127.0.0.1A short descriptor to be shown on bank statement of the customer. Please refer to the integration guide for the format requirements.
A reference specified by the merchant to identify the transaction.
7a1db7a8-6f24-4bc5-a51b-cef33fc05140The full user agent string of the device the customer used to submit the transaction.
A reference used by the merchant to typically capture a description of the service provided. It could then be used by the merchant to help locate transactions. One could envision a situation where a merchant is trying to locate a transaction/ receipt but in speaking with the customer, the only (or at least a predominant) detail is what service was rendered
Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to ISO 4217.
Please note that Klarna only supports EURO (EUR) and Danish krone (DKK).
NONE: No SCA required.WALLET: Depend on the wallet SCA mechanism. For Google Pay this means that MasterCard will shift liability, Visa will not.FORCE_3DS: Do an additional 3DS step regardless of whether the wallet indicates the token is SCA-compliant.
WALLETPossible values: Use this field to request your transaction to be exempted from the application of the Strong Customer Authentication (SCA). Be advised that the use of this field may result to your liability in case of fraudulent transaction. Possible Values: 1 - Low value payment 2 - Acquirer Transaction Risk Analysis 3 - Trusted beneficiary exemption 4 - Secure Corporate Payment (SCP) exemption 5 - Merchant Initiated Transaction 6 - SCA Delegation.
NOTE: This only applies when sca_compliance_level = NONE
The MobilePay Payment Initiation Response.
Bad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
Swish
A value you specify that uniquely identifies this transaction. This must be used to trigger a reversal if there is a timeout.
63bbc548-d2de-4546-b106-880a5018461cThe identifier of merchant entity you want to process the transaction request with. Entity Id can be located on the organization level as Organization ID (Administration > Organizations > [Organization] > Organisation ID value)
30b8bec8-5042-4e67-939c-5453fbe41711The Phone Number registered with Swish Mobile APP. This field is required for ECommerce flow, not needed MCommerce flow.
+31-6-11223344Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
150The ID of a customer.
0a57b387-2ba7-4f65-be2f-e176bb49d2ceThe IP Address of the customer where the transaction was initiated.
127.0.0.1A short descriptor to be shown on bank statement of the customer and also shown in the Swish application. Max 50 chars, allowed characters are the letters a-ö, A-Ö, the numbers 0-9 and the special characters :;.,?!()” and space
A reference specified by the merchant to identify the transaction.
7a1db7a8-6f24-4bc5-a51b-cef33fc05140The full user agent string of the device the customer used to submit the transaction.
A reference used by the merchant to typically capture a description of the service provided. It could then be used by the merchant to help locate transactions. One could envision a situation where a merchant is trying to locate a transaction/ receipt but in speaking with the customer, the only (or at least a predominant) detail is what service was rendered
Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to ISO 4217.
Please note that Swish only supports Swedish krona (SEK).
The Swish Payment Initiation Response.
Bad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
OP Online Payment
Get Available Banks
The OP Online Payment list of Banks Response.
Bad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
Initiate OP Online Payment
A value you specify that uniquely identifies this transaction. This must be used to trigger a reversal if there is a timeout.
63bbc548-d2de-4546-b106-880a5018461cThe identifier of payment provider contract you want to process the transaction request with.
30b8bec8-5042-4e67-939c-5453fbe41711OP bank ID for the bank to be used
Bank name for the selected Bank
Amount is charged without a decimal place e.g. $1.5 = 150. Currencies can have different decimals/exponentials, see Currencies Section for more details. For Account Verification transactions, provide 0 as value for this field.
150The ID of a customer.
0a57b387-2ba7-4f65-be2f-e176bb49d2ceA short descriptor to be shown on the invoice of the customer. Please refer to the integration guide for the format requirements.
A reference specified by the merchant to identify the transaction.
7a1db7a8-6f24-4bc5-a51b-cef33fc05140The full user agent string of the device the customer used to submit the transaction.
Three-letter ISO 4217 alphabetical currency code. e.g. USD. Values correspond to ISO 4217.
Deprecated: BYR (replaced by BYN), FRF (replaced by EUR), LTL (replaced by EUR), LVL (replaced by EUR), MRO (replaced by MRU), STD (replaced by STN), USS (no replacement), VEF (replaced by VES), ZMK (replaced by ZMV) and BTC (Bitcoin only supported as Crypto Amount).
The BCP-47 language tag. Composed of:
- The ISO-639 alpha-1 or ISO-639 alpha-2 language code
- (Optional) The ISO-15924 script tag
- The ISO-3166 alpha-2 country code
es-419this message will be shown on OP's payment list
redirect url for successful payments
redirect url for cancelled payments
redirect url for rejected payments
A settlement reference specified by the merchant to identify the transaction including checksum digit.
12345678912345680000Pattern: ^[0-9]{4,20}$The OP Online Payment Initiation Response.
Bad Request
Unauthorised Request
Forbidden Request
Not Found Request
Internal Error
Was this helpful?
