TRANS|POST|JITscope. So something like this:
PASSif you intend to let the transaction go through. Otherwise supply
CRYPTO-US, this field can be used to supply the asset you wish to liquidate to honor the transaction. This field directly impacts the
extra.assetfield of the funding transaction. See more details in Transactions Extra Schema.
TRANS|POST|JITwebhook url. Your response will indicate to us whether to allow (
"decision": "PASS") or deny (
"decision": "FAIL") the transaction.
total_amount. If a transaction can be partially approved, you will see
to.meta.partial_approval_allowedset to True. Go to Meta Schema of Card Transactions to learn more.
funding_nodes array supplied in the response), then you must both specify the exact
amountto be pulled from each node and ensure that the overall transaction's
total_amountfield equals the sum of the amounts pulled from each funding node. If both of these criteria are not met, the transaction will silently fail.
node_idfor any of the listed funding nodes will also cause the transaction to silently fail.
TRANS|POST|JITwebhook you will need to perform your custom transaction logic, provide funding (if using Instant Auth), and provide a response within 1.00 seconds, or else the transaction will follow the default path of decisioning.
sub_amounts array containing
"amount_type": "AMOUNT_CASH"). You can either approve the full transaction amount, provide Partial Approval only for the purchased goods, or deny the transaction.
SEND-AND-RECEIVEpermissions and that the user
watchlistsflag is not a
MATCH) prior to ever issuing a request from the
TRANS|POST|JITwebhook. This means that you should not receive requests from users who are unable to transact.