PaymentAuthAdjustment

Shows information about an adjustment made to an authorized transaction.

Introduced in API version 51.0.

create(), delete(), describeLayout(), describeSObjects(), getDeleted(), getUpdated(), query(), retrieve(), undelete(), update(), upsert()

  • To access Salesforce Payments objects with the API, your org must have one or more of these licenses: Salesforce Payments, Salesforce Order Management, B2B Commerce, or D2C Commerce. Salesforce Payments objects are available only in Lightning Experience.
  • Type: reference

  • Properties: Create, Filter, Group, Nillable, Sort, Update

  • Description:

    The account for the payment authorization adjustment. Inherited from the payment authorization.

    This is a relationship field.

  • Relationship name: Account

  • Relationship type: relationship

  • Refers to: Account

  • Type: currency
  • Properties: Create, Filter, Sort, Update
  • Description: Amount of adjustment applied to the parent payment authorization.
  • Type: textarea
  • Properties: Create, Filter, Nillable, Sort, Update
  • Description: Users can add comments to provide additional details about a record. Maximum of 1000 characters.
  • Type: datetime
  • Properties: Create, Filter, Nillable, Sort, Update
  • Description: The date that the adjustment occurred.
  • Type: datetime
  • Properties: Create, Filter, Nillable, Sort, Update
  • Description: The date that the adjustment takes effect on the authorization.
  • Type: email
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: Email address of the parent payment authorization owner.
  • Type: datetime
  • Properties: Create, Filter, Nillable, Sort, Update
  • Description: The date and time that the reversal transaction occurred in the payment gateway.
  • Type: textarea
  • Properties: Create, Filter, Nillable, Sort, Update
  • Description: Additional data that can’t be stored in other fields on the payment record. You can use this field for transactions following the initial transaction that creates the payment record. You can use any data that isn’t normalized in financial entities. This field has a maximum length of 1000 characters and can store data as JSON or XML.
  • Type: string
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: Unique transaction ID created by the payment gateway.
  • Type: string
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: Gateway-specific result code. Must be mapped to a Salesforce-specific result code
  • Type: string
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: Description of the gateway’s result code. This field is useful for providing more information around why the gateway returned a certain result code.
  • Type: string
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: The IP address of the user who initiated the payment adjustment.
  • Type: string
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: The MAC address of the person who initiated the payment.
  • Type: string
  • Properties: Autonumber, Defaulted on create, Filter, idLookup, Sort
  • Description: System-provided unique ID for a payment authorization adjustment record.
  • Type: reference

  • Properties: Create, Filter, Group, Sort, Update

  • Description:

    ID of the payment authorization on which the adjustment occurred.

    This is a relationship field.

  • Relationship name: PaymentAuthorization

  • Relationship type: masterdetail

  • Refers to: PaymentAuthorization

  • Type: reference

  • Properties: Create, Filter, Group, Nillable, Sort, Update

  • Introduced: API version 57.0

  • Description:

    ID of the payment intent record.

    This field is a relationship field.

  • Relationship name: PaymentIntent

  • Relationship type: relationship

  • Refers to: PaymentIntent

  • Type: phone
  • Properties: Create, Filter, Group, Nillable, Sort, Update
  • Description: Phone number of the customer who initiated the authorization adjustment.
  • Type: picklist
  • Properties: Create, Filter, Group, Restricted picklist, Sort, Update
  • Description: Defines whether the payment has been made outside of the payment platform.
  • Possible values:
    • External — External — Transactions happened outside of the Salesforce payments platform.
    • Salesforce — Salesforce — Salesforce made and recorded an external call to the payment gateway.
  • Type: picklist
  • Properties: Create, Filter, Group, Nillable, Restricted picklist, Sort, Update
  • Description: Salesforce-specific result code that can map to one or more gateway result codes. We recommend configuring the payment gateway adapter layer to map gateway result codes to the appropriate Salesforce result code.
  • Possible values:
    • Decline — Decline — The gateway call failed, but it might work if the transaction is attempted again. For example, the customer had insufficient funds or briefly lost their connection.
    • Indeterminate — Indeterminate — The gateway didn’t respond to the call. This response usually happens when Salesforce times out while waiting for a response from the gateway.
    • PermanentFail — PermanentFail — The gateway call failed and won’t work even if tried again. Gateway calls fail permanently for one of two reasons: Hard Decline: The customer’s payment account has been closed or terminated. Fraud: The gateway recognized the payment or payment method as known fraud.
    • RequiresReview — RequiresReview — The customer bank requires more information before completing the payment.
    • Success — Success — The gateway call succeeded.
    • SystemError — SystemError — Salesforce ended the payment request before receiving a response. For example, Salesforce lost credentials or access to its server. Salesforce ends payment calls if it doesn’t receive a response from the gateway within two minutes.
    • ValidationError — ValidationError — Customer payment data was incorrect, such as a misspelling in the credit card address or an incorrect CVV.
  • Type: picklist

  • Properties: Create, Filter, Group, Restricted picklist, Sort, Update

  • Description:

    Defines the state of the payment authorization reversal.

    Users can manually change the Status field’s values as follows:

    • Draft to Processed
    • Processed to Canceled
    • Draft to Canceled
  • Possible values:

    • Canceled — Canceled — The payment authorization reversal has been canceled. The parent authorization has returned to its pre-reversal balance.
    • Draft — Draft
    • Pending — Pending
    • Processed — Processed — The payment authorization reversal has been finalized.
  • Type: picklist

  • Properties: Create, Filter, Group, Restricted picklist, Sort, Update

  • Description:

    Defines how the customer used the reversal.

    Possible value is:

  • Possible values:

    • Reversal — Reversal