Commerce Hub Bad Request souce.pinBlock must not be null

rholstad commented 9 months ago

Product

Commerce Hub

Page

https://developer.fiserv.com/product/CommerceHub/docs/?path=docs/Resources/API-Documents/Payments/Charges.md&branch=main#tab-source

Description

Since at least late last week, Commerce Hub Charge requests have been failing with the error

[
 {
  "type": "GATEWAY",
  "field": "source.pinBlock",
  "code": "107",
  "message": "Must not be null"
 }
]

The documentation does not mention a source.pinBlock parameter. When sending source.pinBlock as an empty string, the error is

[
 {
  "type": "GATEWAY",
  "field": "source.pinBlock",
  "code": "100",
  "message": "Invalid or Missing Field Data"
 }
]

When sending source.pinBlock as an integer, boolean, or non-empty string, the error is

[
 {
  "type": "GATEWAY",
  "field": "source.pinBlock",
  "code": "101",
  "message": "Unknown field data in object"
 }
]

When sending source.pinBlock as an Object matching the example for Payment EMV PIN Based Transactions, the error is again

[
 {
  "type": "GATEWAY",
  "field": "source.pinBlock",
  "code": "107",
  "message": "Must not be null"
 }
]

Expected Behaviour

Charge request should be successful

Operating system

iOS 17.1.2

Browser

iPhone SE

Region

No response

minh-pham1 commented 9 months ago

Hello @rholstad! Seems like the Commerce Hub team might have missed updating this in their documentation. I'll assign this ticket to the relevant point of contact and they can assist you further. Thank you!

rholstad commented 9 months ago

@minh-pham1 I opened an analogous issue on the Tap to Pay SDK GitHub where the Engineering team has been working this problem.

Fiserv / Support