A verification reporting whether the payment method has passed your fraud rules and the issuer has ensured it is associated with a valid account.
createdTimestampDate and time at which the verification was created.
gatewayGatewayThe reason the verification was rejected. This will only be set if status is GATEWAY_REJECTED.
idID!Non-nullUnique identifier.
legacyID!Non-nullLegacy unique identifier.
merchantIDThe merchant account used for the verification.
networkPaymentFields describing the network response to the verification request.
paymentPaymentThe multi-use payment method that was verified, if it was vaulted. The details of this PaymentMethod may have changed since it was verified.
paymentPaymentSnapshot of payment method details that were verified. This will always be present.
paymentVerificationDetails unique to the verification based on payment method type being verified.
processorVerificationDetailed response information from the processor. Will not be present if the verification was rejected prior to contacting the processor.
riskRiskRisk data evaluated for this verification.
statusVerificationThe current status of this verification, indicating whether the verification was successful. Braintree recommends only vaulting payment methods that are successfully verified.
amountMonetaryDepending on the type of payment method being verified, some verifications do not have an amount. On a credit card verification, use paymentMethodVerificationDetails.amount instead.
For a credit card, the amount used when performing the verification.
ConfirmObjectverificationNodeInterfacePossible typeRequestObjectverificationUpdateObjectverificationUpdateObjectverificationUpdateObjectverificationVaultObjectverificationVerificationObjectnodeVerifyObjectverificationtype 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
}