Update a transaction
Manually updates a transaction.
transactions.write scope.Authorizations
Headers
Path Parameters
Body
Allows for passing optional configuration per connection to take advantage of connection specific features. When provided, the data is only passed to the target connection type to prevent sharing configuration across connections. Please note that each of the keys this object are in kebab-case, for example cybersource-anti-fraud as they represent the ID of the connector. All the other keys will be snake case, for example merchant_defined_data or camel case to match an external API that the connector uses. If provided, the whole value will be overridden.
Response
Successful Response
A full transaction resource.
The base62 encoded transaction ID. This represents a shorter version of this transaction's id which is sent to payment services, anti-fraud services, and other connectors. You can use this ID to reconcile a payment service's transaction against our system. This ID is sent instead of the transaction ID because not all services support 36 digit identifiers.
"default"
The status of the transaction for the payment_method. The status may change over time as asynchronous processing events occur.
processing, authorization_succeeded, authorization_declined, authorization_failed, authorization_voided, authorization_void_pending, capture_succeeded, capture_pending, buyer_approval_pending "authorization_succeeded"
The outcome of the original intent of a transaction. This allows you to understand if the intent of the transaction (e.g. capture or authorize) has been achieved when dealing with multiple payment instruments.
pending, succeeded, failed "succeeded"
The method used for the transaction.
abitab, affirm, afterpay, alipay, alipayhk, applepay, arcuspaynetwork, bacs, bancontact, bank, bcp, becs, bitpay, blik, ach, boleto, boost, breb, capitec, card, cashapp, cashappafterpay, chaseorbital, clearpay, click-to-pay, custom_push, custom_redirect, custom_tokenize, dana, dcb, dlocal, duitnow, ebanx, eckoh, efecty, eps, everydaypay, gcash, gem, gemds, gift-card, giropay, givingblock, gocardless, googlepay, googlepay_pan_only, gopay, grabpay, ideal, interac, kakaopay, kcp, khipu, klarna, konbini, latitude, latitudeds, laybuy, linepay, linkaja, maybankqrpay, mercadopago, multibanco, multipago, nequi, netbanking, network-token, nupay, oney_10x, oney_12x, oney_3x, oney_4x, oney_6x, onlinebankingcz, onelink, ovo, oxxo, p24, pagoefectivo, paybybank, payid, paymaya, paysquad, paypal, paypaldirectorder, paypalpaylater, paypay, payto, payvalida, paze, picpay, pix, plaid, pse, rabbitlinepay, razorpay, rapipago, redpagos, scalapay, sepa, servipag, seveneleven, sezzle, shopeepay, singteldash, smartpay, sofort, spei, stitch, swish, stripe, stripedd, stripetoken, tapi, tapifintechs, thaiqr, touchngo, truemoney, trustly, trustlyeurope, upi, venmo, vipps, waave, webpay, wechat, wero, yape, zippay "card"
The response code received from the payment service for the Address Verification Check (AVS). This code is mapped to a standardized Gr4vy AVS response code.
match, no_match, partial_match_address, partial_match_postcode, partial_match_name, unavailable "match"