> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/circulation-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/circulation-user-manual/14-appendix-b-file-formats/file-mapping-data-elements/payment-authorization.md).

# Payment Authorization

The following data elements can be used with the “PymtAuthor” usage.

<table><thead><tr><th width="212.11060433295327">Data Element</th><th width="476.4285714285714">Description</th></tr></thead><tbody><tr><td>Abort Status</td><td>Indicates whether the payment was processed.</td></tr><tr><td>Account Number</td><td>Account number for bank draft payments/declines.</td></tr><tr><td>Address Verification</td><td>Indicates whether the subscriber’s address has been verified.</td></tr><tr><td>Authorization Number</td><td>Payment authorization number, typically supplied for credit card payments.</td></tr><tr><td>BACS Originator ID</td><td>Bank originator ID for draft payments/declines.</td></tr><tr><td>Bank Number</td><td>Bank number for draft payments/declines.</td></tr><tr><td>Batch Count</td><td>The total number of records in the batch.</td></tr><tr><td>Batch Date</td><td>The date the batch was created.</td></tr><tr><td>Batch Total</td><td>The total amount for the payment batch.</td></tr><tr><td>Beginning Sequence</td><td>This data element is not currently used.</td></tr><tr><td>Credit Card Number</td><td>The subscriber’s credit card number.</td></tr><tr><td>Edgil ID</td><td>ID assigned to the payment by the Edgil system.</td></tr><tr><td>Ending Sequence</td><td>This data element is not currently used.</td></tr><tr><td>File Sequence</td><td>This data element is not currently used.</td></tr><tr><td>Filler</td><td>Filler denotes blank fields or information that will not be used in Circulation; these fields will be ignored.</td></tr><tr><td>Merchant ID</td><td>Credit card merchant ID</td></tr><tr><td>Record Identifier**</td><td>Field that identifies the record type, for example “D” to indicate a detail record. This must be the first field in the record.</td></tr><tr><td>Reference Number</td><td>Unique customer reference (could include account number).</td></tr><tr><td>Remarks</td><td>Remarks.</td></tr><tr><td>Response Message</td><td>Payment authorization response text.</td></tr><tr><td>Subscription ID</td><td>Subscriber’s account ID in Circulation.</td></tr><tr><td>Tran Amount*</td><td>Payment amount.</td></tr><tr><td>Tran Code</td><td>Transaction code that describes the type of payment.</td></tr><tr><td>Tran Date</td><td>Date of payment.</td></tr><tr><td>Tran Number</td><td>Payment transaction number.</td></tr><tr><td>Trans Sequence</td><td>This data element is not currently used.</td></tr><tr><td>Tran Status</td><td>Status of payment (authorized, rejected, etc.).</td></tr></tbody></table>

> **\*** *Field is required*
>
> **\*\*** *Field is required if a record identifier is entered on the record type setup screen.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.navigaglobal.com/circulation-user-manual/14-appendix-b-file-formats/file-mapping-data-elements/payment-authorization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.