The following guide outlines bank statement descriptor examples for each primary "segment" of Astra payment solution. Per segment, where applicable, we provide an example of what the Sender and Receiver will generally see on their bank statement.

For this guide, we'll use the following values for each example:

• Merchant of Record: ASTRA

• Client / Program Name: OtusFi

• Client Correlation ID: 1a2b3c4d5e

ACH Debit & ACH Credit

What the Sender & Receiver Sees

Statement Descriptor Example: OtusFi - 1a2b3c4d5e

Statement Descriptor Format: <client name> - <client_correlation_id>

Statement Descriptor Breakdown:

• Client Name:

  • Description: The name of the program, which the program defines through their Astra Dashboard

  • Example: OtusFi

• Client Correlation ID:

  • Description: An optional correlation id that will be added to ACH or Debit Addenda. This is a unique string defined by the program at the Routine level.

  • Example: 1a2b3c4d5e (truncated after 10 characters).

    • Note: if no Client Correlation ID is provided, the Client Name is used. The statement descriptor would appear as: OtusFi - OtusFi

Debit AFT & Debit OCT

What the Sender & Receiver Sees

Statement Descriptor Example: ASTRA*OtusFi abcd

Statement Descriptor Format: <Merchant of Record>*<client name> <client_correlation_id>

Statement Descriptor Breakdown:

• Merchant of Record:

  • Description: The merchant of record. Astra Finance is the merchant of record for all programs.

  • Example: ASTRA

• Client Name:

  • Description: The name of the program, which the program defines through their Astra Dashboard

  • Example: OtusFi

• Client Correlation ID:

  • Description: An optional correlation id that will be added to ACH or Debit Addenda. This is a unique string defined by the program at the Routine level.

  • Example: abcd (truncated after 8 characters).

    • Note: Client Correlation IDs for Debits (AFTs / OCTs) are limited to 8 characters. IDs longer than 8 characters will be truncated.

    • Note: Starting October 1st (2025), in order to comply with Visa network guidelines, Astra has scrubbed Routine request client_correlation_id values of all numbers, spaces, and special characters. For this example, the Client Correlation ID would appear as abcd after scrubbing.

    • Note: if no Client Correlation ID is provided, the Client Name is used. The statement descriptor would appear as: ASTRA*OtusFi - OtusFi

RTP & FedNow (Real-Time) Payments to a Bank Account, from an FBO+ Account

What the Receiver Sees:

Statement Descriptor Example: REAL TIME PAYMENT CREDIT RECD FROM ABA/CONTR BNK-021214891 FROM: BNF-Astra REF: 90076a2f70664463 INFO: TEXT-/VXR/00100000044507454 IID: 20240801021214273P1B36FD99142423069 RECD: 15:36:43 TRN: 0806761214G

Statement Descriptor Format: REAL TIME PAYMENT CREDIT RECD FROM ABA/CONTR BNK-[Bank ABA] FROM: BNF-[BeneficiaryName] REF: [ReferenceId] INFO: TEXT-[AdditionalInfo] IID: [InternalId] RECD: [Timestamp] TRN: [TransactionNumber]

Statement Descriptor Breakdown:

1. Transaction Type

• Description: Specifies the nature of the payment. Indicates that this is an incoming real-time payment (RTP) credit that has been received

• Example: REAL TIME PAYMENT CREDIT RECD

2. Originating Bank Identifier

• Description: Identifies the source bank. Identifies the bank that sent the payment using the ABA routing number (021214891). "CONTR BNK" likely refers to the contributing or correspondent bank involved in the transfer

• Example: FROM ABA/CONTR BNK-021214891

3. Sender Name (Beneficiary Name)

• Description: Indicates who sent the payment and who is the sender of the funds. "BNF" stands for Beneficiary Name, in this case, "Astra."

• Example: FROM: BNF-Astra

4. Reference Number

• Description: Used to facilitate tracking and reconciliation. It’s a unique reference number associated with the transaction for tracking and reconciliation purposes

• Example: REF: 90076a2f70664463

5. Payment Information

• Description: Provides additional context for internal or external use. Additional information related to the payment, which could include internal tracking codes, customer references, or transaction metadata

• Example: INFO: TEXT-/VXR/00100000044507454

6. Instruction Identifier (IID)

• Description: Assists in process tracking. A unique identifier for the payment instruction, possibly including date information and other transaction-specific identifiers

• Example: IID: 20240801021214273P1B36FD99142423069

7. Received Timestamp

• Description: The exact time the payment was received, in this case, 3:36:43 PM

• Example: RECD: 15:36:43

8. Transaction Reference Number (TRN)

• Description: A unique transaction reference number for tracking, auditing, or resolving disputes related to the payment

• Example: TRN: 0806761214G

Same Day (T+0) or Next Day (T+1) ACH Credits to an External Bank Account, from an FBO+ Account

What the Receiver Sees:

Statement Descriptor Example: Astra Inc 2FG5T2IXLB ACH CCD ID: 5041340341 REF: A3561156MZEF

Statement Descriptor Format: OriginatorName + Description + Rail + SecCode + "ID: " + OriginatorIdentification + “REF: “ + ReferenceId

Statement Descriptor Breakdown:

1. Originator Name

• Description: Refers to the name of the entity that initiates the ACH payment or debit, the name of which stems from FBO Account name

• Example: Astra Inc

2. Description

• Description: The ACH Addenda. Its primary purpose is to convey essential information that facilitates payment reconciliation and processing

• Example: 2FG5T2IXLB

3. Rail

• Description: The payment network or infrastructure used to process the transaction. Payment rails are the underlying systems that facilitate the movement of money between financial institutions. For ACH transactions, the ACH rail specifically refers to the Automated Clearing House network. 

• Example: ACH

4. SecCode

• Description: ACH: A three-letter code that identifies the type of ACH transaction and the authorization method used and defines Transaction Type. It specifies whether the payment is a debit or credit and whether it is for a consumer or business

  • PPD (Prearranged Payment and Deposit): Consumer transactions like direct deposits and bill payments

    • ACH Credit, Recipient is Personal -> PPD

  • CCD (Corporate Credit or Debit): Business-to-business (B2B) payments

    • ACH Debit, Recipient is Business -> CCD

    • ACH Credit, Recipient is Business -> CCD

  • WEB (Internet-Initiated Entry): Online consumer payments

    • ACH Debit, Recipient is Personal -> WEB

• Example: CCD

5. Originator Identification

• Description: A unique identifier assigned to the entity initiating the ACH transaction (the Originator). It is typically a 10-digit company ID (sometimes called the Company Identification Number) provided by the bank or ACH operator when the Originator is set up to send ACH transactions. This ID helps Receiving Depository Financial Institutions (RDFIs) and NACHA track the source of the ACH entry.

• Example: 5041340341

6. Reference 

• Description: A unique identifier used to track an individual ACH transaction. It is often assigned by the Originating Depository Financial Institution (ODFI) and may appear in ACH reports to help match transactions. It does not have a standard format across all banks but often includes a unique combination of numbers and letters to distinguish the transaction.

• Example: A3561156MZEF

Note: A Reference ID in RTP or FedNow payments is a unique identifier assigned to a transaction for tracking, reconciliation, and troubleshooting. It ensures the payment can be easily identified across systems and is used in receipts, notifications, and inquiries.

Note: Additional Info in RTP or FedNow payments is optional metadata providing extra context, such as tracking IDs, invoice numbers, or payment notes, to help recipients identify or reconcile the transaction.