You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to make sense of this page in the documentation. It specifies, among others, a Product Number column and a Brand column in the XLSX reports, without a mapping for which API field the merchant should use for specifying them.
Scrolling up a little bit on the page describing the report fields, v1 appears to contain both Product Number and Brand. in V2 contains Brand, and the ProductCategory field is described as A product number .., so perhaps ProductCategory maps to ProductNumber?
I've filed a separate issue (#654) about adding ProductCategory to this SDK (via PayeeInfo) - perhaps that will populate the Product Number column (if you could verify that'd be great), but what is the right way of passing in Brand? It's described as Branding information as sent by merchant to Swedbank Pay, so it seems like there ought to be a way.
The text was updated successfully, but these errors were encountered:
I'm trying to make sense of this page in the documentation. It specifies, among others, a
Product Number
column and aBrand
column in the XLSX reports, without a mapping for which API field the merchant should use for specifying them.Neither of the two are listed in the documentation for capture.
Scrolling up a little bit on the page describing the report fields, v1 appears to contain both
Product Number
andBrand
. in V2 containsBrand
, and theProductCategory
field is described asA product number ..
, so perhapsProductCategory
maps toProductNumber
?I've filed a separate issue (#654) about adding
ProductCategory
to this SDK (viaPayeeInfo
) - perhaps that will populate theProduct Number
column (if you could verify that'd be great), but what is the right way of passing inBrand
? It's described asBranding information as sent by merchant to Swedbank Pay
, so it seems like there ought to be a way.The text was updated successfully, but these errors were encountered: