Skip to content

Failed transaction side effects #434

Closed
@mjallday

Description

@mjallday

To ease debugging card declines we at Balanced propose creating transactions in a failed state if a user attempts to debit a card.

This is the default behavior in revision 1.1 but we believe there is enough benefit in doing this for users of revision 1.0 of the API as well.

Doing so would change the behavior of the current API in one of two ways:

  1. Indexing debits (GET /v1/marketplaces/MP123123/debits) would begin returning debits with a failed state whenever a 402 response is received when trying to create a debit.
  2. Indexing debits (GET /v1/marketplaces/MP123123/debits) would only return debits in a failed state when explicitly queried for them. e.g. GET /v1/marketplaces/MP123123/debits?status=failed.

Implementing the first behaviour would mean that users would begin to see debits returned when there previously were none.

Implementing the second behaviour would mean that bank account debits that failed would begin to not be returned by default unless explicitly queried for.

Potentially we could opt for a 3rd behaviour, returning only failed bank account debits and hiding failed card debits but this seems (to me at least) to avoid the principle of least surprise.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions