# Find one Transaction `GET /v2/transactions/{id}` Core API v2, Transactions. Retrieve a Transaction by its ID **Authentication:** Send `Authorization: Bearer `. To authenticate, generate a Secret API Key from your ODUS Dashboard and include it in the `Authorization` header as follows: `Authorization: Bearer ` ## Parameters ### Path parameters - `id` (string, required) ## Responses ### `200` OK Type: object (TransactionDTO). - `createdAt` (string (date-time), required): The date and time when the entity was created. Example: `2024-02-18T12:00:00Z`. - `updatedAt` (string (date-time), required, nullable): The date and time when the entity was last updated. Example: `2024-02-21T12:15:00Z`. - `metadata` (map of string to string, nullable): Metadata used by merchants to store additional information about the entity. - `id` (string, required): The unique identifier of the transaction. - `status` (string, required): Current status of the transaction. One of `pending`, `confirmation_requested`, `authorized`, `failed`. Example: `authorized`. - `authentication` (string, required): How far the transaction got through customer authentication — 3-D Secure for a card, the equivalent payer-action step for a redirect-based method. `not_requested` when the gateway never asked for it, so an absent challenge is distinguishable from a failed one. One of `not_requested`, `pending`, `succeeded`, `failed`. Example: `not_requested`. - `amount` (number, required): Transaction amount in minor currency units (e.g., 1500 for $15.00) Example: `1500`. - `initiator` (string, required): The initiator of the transaction. One of `customer`, `merchant`. Example: `customer`. - `statementDescriptor` (string, nullable): The statement descriptor that will appear on the customer's statement. Only available from the dashboard or the API using a secret key. Example: `Hello World`. - `statementDescriptorSuffix` (string, nullable): The statement descriptor suffix, appended to your account's descriptor by gateways that support a per-payment suffix. Only available from the dashboard or the API using a secret key. Example: `PRO PLAN`. - `amountReversed` (number, required): The amount that has been reversed by refunds or voids. Example: `0`. - `amountCaptured` (number, required): The amount that has been captured. Example: `1500`. - `isReversed` (boolean, required): Whether the transaction has been reversed. Example: `false`. - `isFullyReversed` (boolean, required): Whether the transaction has been fully reversed. Example: `false`. - `isCaptureFailed` (boolean, required): Whether the capture operation failed. Example: `false`. - `isReverseFailed` (boolean, required): Whether the reverse operation failed. Example: `false`. - `isRefundFailed` (boolean, required): Whether the refund operation failed. Example: `false`. - `isVoidFailed` (boolean, required): Whether the void operation failed. Example: `false`. - `isCaptured` (boolean, required): Whether the transaction has been captured. Example: `true`. - `isChargebacked` (boolean, required): Whether the transaction has a chargeback recorded. Example: `false`. - `chargebackRecordedAt` (string (date-time), nullable): The timestamp when a chargeback was recorded for this transaction. Example: `2026-01-15T10:30:00.000Z`. - `captureMethod` (string, required): Capture method used for this transaction. One of `automatic`, `automaticDelayed`, `manual`. Example: `automatic`. - `captureDelay` (number, required, nullable): Delay in days before capture occurs. Only applicable for 'automaticDelayed' capture method. Example: `0`. - `currency` (string, required): Currency of the transaction. One of `usd`, `eur`, `gbp`, `cad`, `aud`, `pln`, `czk`, `sek`, `dkk`. Example: `usd`. - `processorId` (string, nullable): The external transaction ID from the payment processor. Only available from the dashboard or the API using a secret key. Example: `ch_1J8lZpJ9j1bSv2Jr6sVjXZ1N`. - `outcome` (object, nullable): Outcome details from the gateway operation. Only available from the dashboard or the API using a secret key. - `status` (string, required): One of `success`, `partial`, `failure`. - `errorCode` (string, required, nullable): One of `internal_error`, `not_supported`, `generic_decline`, `insufficient_funds`, `authentication_failed`, `authentication_cancelled`, `authentication_unavailable`, `cancelled`, `invalid_card_details`, `expired_card`, `authentication_required`, `transaction_not_permitted`, `generic_issuer_error`, `generic_processor_error`, `processor_rate_limited`, `processor_timeout`, `fraud_suspected`, `card_restricted`, `authentication_rejected`, `payment_method_unusable`, `generic_hard_decline`, `already_captured`, `merchant_account_restricted`, `merchant_configuration_error`, `invalid_request`, `blocked_by_policy`, `order_not_permitted`, `stored_credential_revoked`. - `errorMessage` (string, required, nullable) - `safeErrorMessage` (string, required, nullable) - `declineType` (string, required, nullable): One of `soft_decline`, `hard_decline`, `not_attempted`. - `retryStrategy` (string, required, nullable): One of `never_retry`, `retry_with_new_payment_method`, `retry_after_delay`, `retry_immediately`. - `specialCode` (string, required, nullable): One of `confirmation_requested`. - `authCode` (string, required, nullable) - `processorCode` (string, required, nullable) - `processorMessage` (string, required, nullable) - `payment` (string, required): The ID of the payment this transaction belongs to. - `gatewayProfile` (object): Gateway profile used for this transaction. Only available from the dashboard or the API using a secret key. - `createdAt` (string (date-time), required): The date and time when the entity was created. Example: `2024-02-18T12:00:00Z`. - `updatedAt` (string (date-time), required, nullable): The date and time when the entity was last updated. Example: `2024-02-21T12:15:00Z`. - `metadata` (map of string to string, required, nullable): Metadata used by merchants to store additional information about the entity. - `id` (string, required): ID of the Gateway Profile. Example: `gwp_2QC7PqoUeOxQEWscJJt6B3PkvyL`. - `active` (boolean, required): Whether the gateway profile is active and available for processing. Example: `true`. - `title` (string, required): Title of the Gateway Profile. Example: `Profile #1`. - `integration` (string, required): Associated Gateway Integration. One of `stripe`, `adyen`, `checkout`, `paypal`. Example: `stripe`. - `environment` (string, required, nullable): The environment the gateway profile operates in. One of `live`, `test`. Example: `test`. - `supportedPaymentMethods` (array of string, required): Supported payment methods for the Gateway Profile. Each item: One of `card`, `paypal`, `applePay`. - `execution` (string, nullable): The cascade execution associated with this transaction. Only available from the dashboard or the API using a secret key. - `paymentMethod` (object, required): The payment method used for this transaction. - `createdAt` (string (date-time), required): The date and time when the entity was created. Example: `2024-02-18T12:00:00Z`. - `updatedAt` (string (date-time), required, nullable): The date and time when the entity was last updated. Example: `2024-02-21T12:15:00Z`. - `metadata` (map of string to string, nullable): Metadata used by merchants to store additional information about the entity. - `id` (string, required): The ID of the payment method. Example: `pm_2QC7PqoUeOxQEWscJJt6B3PkvyL`. - `type` (string, required): The type of the payment method. One of `card`, `paypal`, `applePay`. Example: `card`. - `customer` (string, required, nullable): The ID of the customer who this payment method belongs to. Example: `cus_2QC7PqoUeOxQEWscJJt6B3PkvyL`. - `isDefault` (boolean, required): Whether the payment method is the default one for the customer. Example: `false`. - `card` (object, required, nullable): The card details of the payment method. Set only when `type` is `card`. - `brand` (string, required, nullable): The brand of the card. One of `visa`, `mastercard`, `amex`, `discover`. Example: `amex`. - `lastFour` (string, required): The last four digits of the card. Example: `1234`. - `bin` (string, required): The card BIN/IIN (Bank/Issuer Identification Number) - 4 to 8 digits. Example: `123456`. - `expMonth` (string, required, nullable): The expiration month of the card (in MM format) Example: `12`. - `expYear` (string, required, nullable): The expiration year of the card (in YYYY format) Example: `2025`. - `cardholderName` (string, required, nullable): The name on the card. Example: `John Doe`. - `applePay` (object, required, nullable): The Apple Pay details of the payment method. Set only when `type` is `applePay`. - `displayName` (string, required, nullable): The display name of the Apple Pay payment method. Example: `MasterCard 1234`. - `customer` (object, required, nullable): The customer associated with this transaction. - `createdAt` (string (date-time), required): The date and time when the entity was created. Example: `2024-02-18T12:00:00Z`. - `updatedAt` (string (date-time), required, nullable): The date and time when the entity was last updated. Example: `2024-02-21T12:15:00Z`. - `metadata` (map of string to string, nullable): Metadata used by merchants to store additional information about the entity. - `id` (string, required): The ID of the customer. Example: `cus_2QC7PqoUeOxQEWscJJt6B3PkvyL`. - `email` (string, required): The email of the customer. Example: `user@gmail.com`. - `name` (string, required, nullable): The name of the customer. Example: `John Doe`. - `phoneNumber` (string, required, nullable): The phone number of the customer. Numbers submitted since normalisation began are stored in E.164 format (`+` followed by digits) when they could be validated; any other number is returned as it was sent. Example: `+12015550123`. - `dateOfBirth` (string (date), required, nullable): The date of birth of the customer. Pattern `^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))$`. Example: `2020-01-01`. - `gender` (string, required, nullable): The gender of the customer. One of `male`, `female`, `other`. Example: `male`. - `restrictMit` (boolean): Whether the customer is restricted from making merchant-initiated payments. Only available from the dashboard or the API using a secret key. Example: `false`. - `restrictCit` (boolean): Whether the customer is restricted from making customer-initiated payments. Only available from the dashboard or the API using a secret key. Example: `false`. - `restrictReason` (string, nullable): Reason for restricting the customer. Only available from the dashboard or the API using a secret key. Example: `Customer restricted due to suspicious activity`. - `isRestricted` (boolean): Whether the customer has at least one restriction applied (either `restrictMit` or `restrictCit`). Only available from the dashboard or the API using a secret key. Example: `true`. ### `202` The merchant is entitled but its environment is not provisioned yet. Provisioning has been kicked off (exactly once) and is in progress; retry the request — it succeeds once the environment is ready. Returned only for identity-token (dashboard) requests bound to a merchant, not for secret-key API calls; any such endpoint can return it while provisioning is underway. Type: object (ProvisioningInProgress). - `status` (string, required): Signals the merchant environment is still being provisioned. One of `provisioning`. - `merchantAccountId` (string, required): The merchant account whose environment is being provisioned. Example: `dAI3aa87ROOeupeBCjNSKCOBOisBCYjB`. ### Errors - `400`: The request was rejected. `type` is `invalid_request_error` when the request itself is at fault — `errors` then lists every problem found, with field-attributable entries prefixed by the field’s path; or `invalid_state_error` when the request was well-formed but the resource is not in a state that allows it. - `401`: No API key was supplied, or the key is not valid. `type` is `authentication_error`. - `403`: The API key is valid but lacks the permission this operation requires. `type` is `permission_error`. - `404`: No resource exists with the requested identifier. `type` is `not_found_error`. - `429`: Too many requests. A limit applies per operation; requests to other operations are unaffected. `type` is `rate_limit_error`. Use the `Retry-After-global` header to know when to retry. - `500`: The request could not be completed because of an unexpected error. `type` is `api_error`. - `503`: The request could not be served right now: the API is temporarily at capacity, or a dependency needed to authorize the request is unavailable — the auth service that verifies credentials, or the entitlement lookup behind it. `type` is `api_error`. It is raised before the operation runs, so the request had no effect, and unlike a plain 500 the condition is transient: retry with backoff. - `504`: The request exceeded the processing time limit and was abandoned. `type` is `api_error` and `code` is `timeout` — unlike a plain 500 the request may still have taken effect, so retry with the same idempotency key rather than blindly. Every error response has the same body: see [Errors](https://docs.odus.com/docs/guides/api-features/errors.md). --- Generated from the Core API v2 OpenAPI document, https://api.odus.com/openapi.v2.json. Interactive page: https://docs.odus.com/docs/api/core/v2/transaction-controller-find-one