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
Using production, we encountered a few instances of the settlementState element returning the value "settlementError". This causes BatchDetails.getSettlementState() to return null because the SDK only allows for the values "settledSuccessfully" or "error", as per the API documentation.
Good catch! As defined in the schema, acceptable values in that element should be settledSuccessfully, settlementError, or pendingSettlement.
I've made the change in the API Reference, although the change won't go live until the next build of the production site (which could be a week or two).
Using production, we encountered a few instances of the settlementState element returning the value "settlementError". This causes BatchDetails.getSettlementState() to return null because the SDK only allows for the values "settledSuccessfully" or "error", as per the API documentation.
<batch> <batchId>XXXXXXXXXX</batchId> <settlementTimeUTC>2017-04-07T02:45:03Z</settlementTimeUTC> <settlementTimeLocal>2017-04-06T19:45:03</settlementTimeLocal> <settlementState>settlementError</settlementState> <paymentMethod>creditCard</paymentMethod> <marketType>eCommerce</marketType> <product>Card Not Present</product> </batch>
The text was updated successfully, but these errors were encountered: