Package com.onlinepayments.domain
Class PaymentReferences
java.lang.Object
com.onlinepayments.domain.PaymentReferences
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionIt allows you to store additional parameters for the transaction in the format you prefer (e.g.-> key-value query string, JSON, etc.) These parameters are then echoed back to you in API GET calls and Webhook notifications.Your unique reference of the transaction that is also returned in our report files.voidsetMerchantParameters(String value) It allows you to store additional parameters for the transaction in the format you prefer (e.g.-> key-value query string, JSON, etc.) These parameters are then echoed back to you in API GET calls and Webhook notifications.voidsetMerchantReference(String value) Your unique reference of the transaction that is also returned in our report files.withMerchantParameters(String value) It allows you to store additional parameters for the transaction in the format you prefer (e.g.-> key-value query string, JSON, etc.) These parameters are then echoed back to you in API GET calls and Webhook notifications.withMerchantReference(String value) Your unique reference of the transaction that is also returned in our report files.
-
Constructor Details
-
PaymentReferences
public PaymentReferences()
-
-
Method Details
-
getMerchantParameters
It allows you to store additional parameters for the transaction in the format you prefer (e.g.-> key-value query string, JSON, etc.) These parameters are then echoed back to you in API GET calls and Webhook notifications. This field must not contain any personal data. -
setMerchantParameters
It allows you to store additional parameters for the transaction in the format you prefer (e.g.-> key-value query string, JSON, etc.) These parameters are then echoed back to you in API GET calls and Webhook notifications. This field must not contain any personal data. -
withMerchantParameters
It allows you to store additional parameters for the transaction in the format you prefer (e.g.-> key-value query string, JSON, etc.) These parameters are then echoed back to you in API GET calls and Webhook notifications. This field must not contain any personal data. -
getMerchantReference
Your unique reference of the transaction that is also returned in our report files. This is almost always used for your reconciliation of our report files. It is highly recommended to provide a single MerchantReference per unique order on your side -
setMerchantReference
Your unique reference of the transaction that is also returned in our report files. This is almost always used for your reconciliation of our report files. It is highly recommended to provide a single MerchantReference per unique order on your side -
withMerchantReference
Your unique reference of the transaction that is also returned in our report files. This is almost always used for your reconciliation of our report files. It is highly recommended to provide a single MerchantReference per unique order on your side
-