Card Real-Time Decisioning
Real-time decision response object
When you receive a real-time decision request, your system must respond with a decision within 3 seconds. The response object contains your authorization decision and any optional parameters based on the decision type. Read more about real-time decisioning.
Object Parameters
decision
enumThe authorization decision. Possible values: approve, partially_approve, decline
decline_reason
enumOptional reason for the decline. Providing a decline reason helps merchants understand why the transaction was declined and can reduce network fees. If not specified, Column will return a generic do not honor response code. Possible values: insufficient_funds, suspected_fraud, stop_payment, require_3ds
funding_account_id
stringThe ID of a bank account on your platform to just-in-time fund the authorization from. Only applicable when decision is approve or partially_approve on an initial purchase authorization on a debit card program with jit_funding_enabled. If the card account's available balance does not cover the approved amount, Column moves the shortfall, plus any amount the card account is overdrawn, from this account into the card account's bank account before approving; the funding is recorded in the card transaction's funding_details and returned to this account, up to the amount the authorization releases, if the authorization is reversed, expires, or clears for less. If this account cannot cover the shortfall, the authorization is declined
partially_approve_amount
numberThe amount to partially approve in the smallest unit of the currency (e.g., cents for USD). Only applicable when decision is partially_approve. The request must support partial approvals (check can_support_partial_approvals in the point of sale details). If partial approval is not supported, the transaction will be declined. Incremental authorizations and reauthorizations do not support partial approval