Authorize.Net Deposit Imports

Last Updated: 2026-07-21

Version: 1.0

Use one Authorize.Net settled batch as the boundary for one VRPlatform deposit. Each settling payment or refund in the batch becomes one deposit line.

Result

For every settled batch with at least one non-zero settling transaction, submit one deposit with:

the Authorize.Net batch ID as uniqueRef
the UTC settlement time, then local settlement time, as date
the team's configured default currency
positive payment lines and negative refund lines
no lines for declined, expired, voided, canceled, or cancelled activity

Authorize.Net amounts are decimal major units. Convert each line to integer minor units before submission.

Authorize.Net Data to Load

Load settled batches for the target date range. For every batch ID, load the transaction list and then the transaction details needed for amount, status, type, order, and customer information.

Authorize.Net value	VRPlatform use
`batch.batchId`	Transaction `uniqueRef`
`batch.settlementTimeUTC`	Preferred transaction `date`
`batch.settlementTimeLocal`	Date when UTC time is absent
`transaction.transId`	Line `uniqueRef`
`transaction.settleAmount`	Preferred line amount
`transaction.authAmount`	Amount when settlement amount is absent
`transaction.amount`	Final amount choice

The provider payload does not currently supply a destination-bank last four, so omit matchBankAccountLast4 unless another authoritative source supplies it.

Filter and Sign Transactions

Exclude transactions whose normalized status is:

declined
expired
voided
canceled
cancelled

Also exclude transaction type voidTransaction.

Treat refundTransaction or a status containing refund as a refund. Make a positive refund amount negative. Preserve an already-negative refund amount.

Transaction	`matchLineTypeClassification`
Payment	`authorizeNet_payment`
Refund	`authorizeNet_refund`

Build the description from the first non-empty value:

order.description
order.invoiceNumber
invoice
bill-to full name
Authorize.net transaction ${transId}

Use transaction-${transId} as the line identity. Add a deterministic numeric suffix if the source repeats that identity within one batch.

Authorize.Net does not expose a dedicated reservation field in this composition. If an active PMS has a recognized reference format in the line description, send the parsed value as matchReservationConfirmationCode. Otherwise omit the hint and allow the line to remain unmatched.

Do not treat an invoice number as a reservation confirmation code without an explicit source contract.

Reconciliation

Store and monitor the line sum:

line total = sum(settling payment and refund lines)

The settled-batch payload used by this composition does not expose a separate authoritative net batch amount. Do not invent an adjustment line. Reconcile the created deposit to the bank settlement when that value becomes available.

End-to-End Example

{
  "batch": {
    "batchId": "batch-1",
    "settlementTimeUTC": "2026-04-01T18:48:19Z",
    "settlementState": "settledSuccessfully"
  },
  "transactions": [
    {
      "transId": "tx-1",
      "transactionType": "authCaptureTransaction",
      "transactionStatus": "settledSuccessfully",
      "settleAmount": "125.50",
      "order": { "description": "Booking ABC123" }
    },
    {
      "transId": "tx-2",
      "transactionType": "refundTransaction",
      "transactionStatus": "refundSettledSuccessfully",
      "settleAmount": "20.00",
      "order": { "invoiceNumber": "INV-101" }
    }
  ]
}

{
  "connectionId": "00000000-0000-0000-0000-000000000002",
  "data": [
    {
      "type": "deposit",
      "currency": "usd",
      "date": "2026-04-01",
      "description": "Authorize.net batch batch-1",
      "uniqueRef": "batch-1",
      "lines": [
        {
          "uniqueRef": "transaction-tx-1",
          "amount": 12550,
          "description": "Booking ABC123",
          "matchLineTypeClassification": "authorizeNet_payment"
        },
        {
          "uniqueRef": "transaction-tx-2",
          "amount": -2000,
          "description": "INV-101",
          "matchLineTypeClassification": "authorizeNet_refund"
        }
      ]
    }
  ]
}

Implementation Checklist

Use the settled batch, not the transaction creation date, as the boundary.
Load transaction details before composing amounts and descriptions.
Exclude every non-settling status and void transaction.
Convert decimal amounts to minor units once.
Force refunds negative.
Use the team's default currency only when the provider batch has no currency.
Do not synthesize a reconciliation adjustment.