# Verification

Object · GraphQL API

A verification reporting whether the payment method has passed your fraud rules and the issuer has ensured it is associated with a valid account.

## Fields

- `id` (`ID!`) — non-null: Unique identifier.
- `legacyId` (`ID!`) — non-null: Legacy unique identifier.
- `paymentMethodSnapshot` (`PaymentMethodSnapshot`): Snapshot of payment method details that were verified. This will always be present.
- `paymentMethod` (`PaymentMethod`): The multi-use payment method that was verified, if it was vaulted. The details of this PaymentMethod may have changed since it was verified.
- `amount` (`MonetaryAmount`) — deprecated since 2019-08-22: For a credit card, the amount used when performing the verification.
- `merchantAccountId` (`ID`): The merchant account used for the verification.
- `status` (`VerificationStatus`): The current status of this verification, indicating whether the verification was successful. Braintree recommends only vaulting payment methods that are successfully verified.
- `processorResponse` (`VerificationProcessorResponse`): Detailed response information from the processor. Will not be present if the verification was rejected prior to contacting the processor.
- `networkResponse` (`PaymentNetworkResponse`): Fields describing the network response to the verification request.
- `createdAt` (`Timestamp`): Date and time at which the verification was created.
- `gatewayRejectionReason` (`GatewayRejectionReason`): The reason the verification was rejected. This will only be set if status is GATEWAY_REJECTED.
- `riskData` (`RiskData`): Risk data evaluated for this verification.
- `paymentMethodVerificationDetails` (`VerificationDetails`): Details unique to the verification based on payment method type being verified.

## Used by

- [ConfirmMicroTransferAmountsPayload](/braintree/graphql/reference/types/confirm-micro-transfer-amounts-payload) — Object; verification
- [Node](/braintree/graphql/reference/types/node) — Interface; Possible type
- [RequestVaultInStoreContext](/braintree/graphql/reference/types/request-vault-in-store-context) — Object; verification
- [UpdateCreditCardBillingAddressPayload](/braintree/graphql/reference/types/update-credit-card-billing-address-payload) — Object; verification
- [UpdateCreditCardCardholderNamePayload](/braintree/graphql/reference/types/update-credit-card-cardholder-name-payload) — Object; verification
- [UpdateCreditCardExpirationDatePayload](/braintree/graphql/reference/types/update-credit-card-expiration-date-payload) — Object; verification
- [VaultPaymentMethodPayload](/braintree/graphql/reference/types/vault-payment-method-payload) — Object; verification
- [VerificationConnectionEdge](/braintree/graphql/reference/types/verification-connection-edge) — Object; node
- [VerifyPaymentMethodPayload](/braintree/graphql/reference/types/verify-payment-method-payload) — Object; verification

## GraphQL definition

```graphql
type Verification implements Node {
  id: ID!
  legacyId: ID!
  paymentMethodSnapshot: PaymentMethodSnapshot
  paymentMethod: PaymentMethod
  amount: MonetaryAmount @deprecated(reason: "Depending on the type of payment method being verified, some verifications do not have an amount. On a credit card verification, use `paymentMethodVerificationDetails.amount` instead.")
  merchantAccountId: ID
  status: VerificationStatus
  processorResponse: VerificationProcessorResponse
  networkResponse: PaymentNetworkResponse
  createdAt: Timestamp
  gatewayRejectionReason: GatewayRejectionReason
  riskData: RiskData
  paymentMethodVerificationDetails: VerificationDetails
}
```

---

[View the complete GraphQL schema on GitHub](https://raw.githubusercontent.com/braintree/graphql-api/refs/heads/master/schema.graphql)