Resolve Wallet Dispute

Carries out an accepted dispute: moves the agreed amount using the outcome the dispute was accepted with.

Call it after Accept Wallet Dispute. The outcome and amount come from the dispute; the body only carries the batchId a
wallet-credit needs. The dispute stays accepted.

  • card-refund: the agreed amount goes back to the card that paid for the load.
  • wallet-credit: the agreed amount is credited to the holder's wallet from your ledger account, as a payment in the
    batch you name (see Credit Wallet). The holder must have finished onboarding.
  • complete-credit: the card load that never reached the wallet is added to it, for its full amount.

Retries. Resolving never moves the money twice. Repeating a card-refund or wallet-credit resolution returns the same
result. Repeating a complete-credit resolution is refused with 409 DISPUTE_OUTCOME_NOT_PERMITTED, because the load
has now reached the wallet.

Requires the Wallet Management permission (see Invite Wallet Holder).

Errors

  • 400 INVALID_BODY: the body is present but is not a JSON object
  • 400 RESOLUTION_INVALID_BATCH: batchId is sent but is not a non-empty string
  • 400 CREDIT_BATCH_REQUIRED: batchId is required for a wallet-credit resolution
  • 400 CREDIT_BATCH_INVALID: the batch does not exist, is archived, or cannot hold credits
  • 404 NOT_FOUND: the dispute does not exist, or is not on one of your wallets
  • 409 DISPUTE_NOT_RESOLVABLE: the dispute has not been accepted
  • 409 DISPUTE_OUTCOME_NOT_PERMITTED: the disputed entry cannot take the accepted outcome. Check Get Wallet Dispute
    Resolution Options; contact Payment Labs support to change the outcome
  • 409 DISPUTE_RESOLUTION_ESCALATED: the load can no longer pay for the outcome, for example because the holder spent
    it. Payment Labs takes the dispute from here; no money moved
  • 409 REFUND_ALREADY_EXISTS, 409 CREDIT_ALREADY_EXISTS: a refund or credit was already made for this dispute by
    another route
  • 409 CUSTOMER_FROZEN: your wallet program is frozen. Contact Payment Labs support
  • 409 HOLDER_NOT_PAYABLE: the holder has not finished onboarding, so a wallet-credit cannot be made yet
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The dispute ID, starting with DS-, as returned by Search Wallet Disputes or the wallet dispute webhooks.

Body Params
string

The batch that holds the payment behind a wallet-credit resolution. Required for wallet-credit; ignored for the other
outcomes. It must be one of your batches and not archived.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json