User Tools

Site Tools


securepayment20

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
securepayment20 [2018/05/03 11:31]
Alexandr Grishin
securepayment20 [2018/05/08 08:36]
Dmitry Karpenko [Request JSON data object description]
Line 110: Line 110:
 | SPPaymentProvider | string | * optional. code of preferred payment provider. EMONEY only. BP/BH (BTC) /  QW (QiWi) / SF (Sofort). if defined, customer will be redirected directly to selected payment gateway | | SPPaymentProvider | string | * optional. code of preferred payment provider. EMONEY only. BP/BH (BTC) /  QW (QiWi) / SF (Sofort). if defined, customer will be redirected directly to selected payment gateway |
 | SPUserVariable | string | * optional | | SPUserVariable | string | * optional |
-| SPPaymentType | string | * optional. additional param for few types. code of crypto currency in case of Crypto (BH). XBT/XBC/LTC |+| SPPaymentType | string | * optional. additional param for few types. code of crypto currency in case of Crypto (BH). XBT/XBC/LTC/​BTG/​DSH/​ETH ​|
  
 The list of request parameters that the Service will sent to the merchant system in S2S message. **Signature** parameter will not appear only for **CHECK** type of S2S message. The list of request parameters that the Service will sent to the merchant system in S2S message. **Signature** parameter will not appear only for **CHECK** type of S2S message.
securepayment20.txt ยท Last modified: 2018/05/08 08:36 by Dmitry Karpenko