Skip to content

Latest commit

 

History

History
28 lines (24 loc) · 3.46 KB

StandaloneTransaction.md

File metadata and controls

28 lines (24 loc) · 3.46 KB

StandaloneTransaction

Properties

Name Type Description Notes
transaction_id string Identifier for this payment transaction given by the merchant. It is not validated for uniqueness by OPG, but may be checked for by some PSPs, thus recommended to be unique.
country string Country where the payment is originating. This influences the choice of the available payment networks. Value format is according to ISO 3166-1 (alpha-2), e.g. "DE", "FR", "US", "GB", etc.
channel string Indicates where the payment request comes from. For example, from a website, from a mobile device, or it is a recurring transaction from the merchant's backend. By default `WEB_ORDER` for this type of transactions. [optional]
division string Division name of this transaction. Merchant can configure multiple divisions via Merchant Configuration API or portal. But there is always one default division that will be used if this property is undefined. Different divisions can be configured with different setup, contracts, payment routes and network options. [optional]
callback \Optile\Model\Callback
customer \Optile\Model\Customer
customer_score int Customer score value in range 0...1000. This value will be used by the system for the decision that some security checks should be enforced or disabled (like 3D Security check). [optional]
client_info \Optile\Model\ClientInfo [optional]
payment \Optile\Model\Payment
products \Optile\Model\Product[] Products (shopping cart) information. [optional]
style \Optile\Model\StandaloneStyle [optional]
preselection \Optile\Model\StandalonePreselection
mandate \Optile\Model\Mandate [optional]
installment \Optile\Model\Installment [optional]
auto_registration bool If set to `true` the account will be registered for further payments. [optional]
allow_recurrence bool If set to `true` the account will be registered for further recurring payments. [optional]
account \Optile\Model\AccountInputData [optional]
encrypted_account string Customer account data encrypted with one of the CSE (Client Side Encryption) keys configured in MCAPI for division of this transaction. Account data should be encrypted according to JOSE standard "RSA-OAEP" + "A256GCM", see RFC-7520. Note that supplying both fields `account` and `encryptedAccount` will cause an error and such operation will be rejected. See Client Side Encryption for further details. [optional]
checkboxes map[string,bool] Map of selected checkboxes; name reflects the checkbox distinguish name, value reflects its state - `true` for selected, `false` for unchecked [optional]

[Back to Model list] [Back to API list] [Back to README]