# Account ACH Details with RTP/FedNow source: https://developer.mastercard.com/open-finance-us/documentation/products/pay/verification-money-transfer/index.md Tip: Account ACH Details now supports [Feedback Loop](https://developer.mastercard.com/open-finance-us/documentation/products/pay/feedback-loop/index.md) which reduces payment failures by securely sharing payment outcome data with Mastercard, enabling us to identify and correct data quality issues. Contact your Customer Success Manager to participate. Retrieve a customer's ACH (Automated Clearing House) details for a specified account. The payment instruction types that the bank account provides are returned. The response indicates whether Real Time Payments (RTP), FedNow Payments (Federal Reserve) and [Tokenized Account Numbers](https://developer.mastercard.com/open-finance-us/documentation/products/pay/verification-money-transfer/index.md#tokenized-account-numbers-tan) (TANs) are enabled. The ACH, RTP and FedNow details can be used for account opening or payment initiation. * The RTP flag indicates if the account can receive and/or send RTPs. It does not indicate if the account or financial institution is Request for Payment (RFP) enabled. * The FedNow flag indicates if the account can receive and/or send instant FedNow payments. It does not indicate if the account or financial institution is Request for Payment (RFP) enabled. * The TAN enabled flag indicates if the Financial Institution leverages a Tokenized Account Number (TAN) for payment initiation. If the account is verified manually using our microdeposit service Account Validation Assistant (AVA), the account is using the real account number and will never be represented by a TAN. Warning: To minimize risk of fraud, we highly recommend verifying the account owner before proceeding with consumer transactions. See [Account Owner Verification](https://developer.mastercard.com/open-finance-us/documentation/products/pay/verification-account-owner/index.md). Note: This is a premium service, billable per every successful API call. Note: Before calling any Account Opening endpoints you should verify the FI concerned supports the service by checking our [Certified Institutions](https://developer.mastercard.com/open-finance-us/documentation/financial-institution/index.md#certified-institutions) list. ## How It Works {#how-it-works} 1. Generate the required credentials to call the API. See [Generate Your Credentials](https://developer.mastercard.com/open-finance-us/documentation/quick-start-guide/index.md#generate-your-credentials) in the Quick Start Guide. 2. Generate an Access Token. See [Create Access Token](https://developer.mastercard.com/open-finance-us/documentation/quick-start-guide/index.md#step-1---create-access-token) in the Quick Start Guide. 3. Create a customer and link them to at least one account. See [Welcome Your First Customer](https://developer.mastercard.com/open-finance-us/documentation/quick-start-guide/index.md#welcome-your-first-customer) in the Quick Start Guide (you will need to connect a checking and savings account using "Finbank" with the username and password "demo_rtn2"). 4. Call `GET /aggregation/v3/customers/{customerId}/accounts/{accountId}/details` with a `customerId` and `accountId` to return the payment instruction details (ACH and, if applicable, RTP/FedNow money transfer details). Diagram account-ach ## API {#api} API Reference: `GET /aggregation/v3/customers/{customerId}/accounts/{accountId}/details` Tip: Some FIs will return a tokenized version of the account number (this is indicated in the response by the `tanEnabled` flag). For details see [Tokenized Account Numbers (TAN)](https://developer.mastercard.com/open-finance-us/documentation/products/pay/verification-money-transfer/index.md#tokenized-account-numbers-tan). ## Fast ACH {#fast-ach} Our Fast ACH solution enables the Get Account ACH Details to give a faster response to those partners who have enrolled for the service, by caching the required data on our server. Fast ACH is offered at no additional charge. When Fast ACH is enabled, we will pre-fetch the account and routing number details during the account linking process. This is advantageous if you have a time-sensitive use case, as in most cases, the data will be available before the user completes the account linking process. There will also be no need to make an API call to refresh customer account data prior to the Get Account ACH Details call when using Fast ACH, as this will have been done when the data was cached. Fast ACH isn't necessary or appropriate for all partners and is not supported for all FIs. While Fast ACH is offered at no additional charge, it does require enrollment. Speak with your Account Manager to determine if Fast ACH is right for your use case and to enroll. Be aware that it might take a few days for the service to be set up for you. We might need to contact you to help decide if Fast ACH is appropriate for your situation. The following sequence diagram shows how Fast ACH, when available, allows the routing data to be fetched and cached during the account linking process: Diagram ach-cached ## Tokenized Account Numbers (TAN) {#tokenized-account-numbers-tan} A TAN is a tokenized version of the account number in the response to the Get Account ACH details call. Chase, PNC, and soon US Bank will return a Tokenized Account Number (TAN) in place of the real account number and routing number (the `tanEnabled` flag in the response indicates when TANs are used). Alert: US Bank are rolling out their move to using TANs April 30, 2026. Ensure that you check the `tanEnabled` flag in the `GET /aggregation/v3/customers/{customerId}/accounts/{accountId}/details` response and handle account numbers accordingly. TANs are specific to each application and therefore provide extra security for the customer. The variances of the TANs returned by Chase, PNC, and US Bank are explained in this table: | Scenario | Chase | PNC | US Bank | |------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | What actions should be taken to keep the TAN valid? | Ensure that the `customerId` is **not** deleted from the Mastercard Open Finance database. Proactively educate end users to avoid revoking data sharing consent from within their Chase banking portal. Accounts with an `aggregationStatusCode` of "0" can be assumed to have valid TANs as this status code indicates that the token has not been revoked. | Ensure that the `customerId` is **not** deleted from the Mastercard Open Finance production platform. Proactively educate end users to avoid revoking data sharing consent (see **"How is a TAN revoked?"** ). Accounts with an `aggregationStatusCode` of "0" can be assumed to have valid TANs as this status code indicates that the token has not been revoked. | No actions are required by data recipients to keep TANs valid for US Bank. | | Do TANs expire? | TANs issued by Chase do not expire. | TANs issued by PNC will expire when data sharing authorization expires. | TANs do not expire or get revoked for reasons other than fraud. | | When does a TAN become invalid? | The TAN becomes invalid when the user explicitly revokes data sharing consent or if the `customerId` or `institutionLoginId` are deleted via the delete customer endpoint. Invalid TANs will cause any new or pending payments using the TAN to fail. | The validity of the TAN is tied to the user's data sharing authorization. Only TANs issued against valid authorizations are eligible for payment. Invalid TANs will cause any new or pending payments using the TAN to fail. | TANs are only revoked when fraud is detected/reported. | | Does a user need to reconsent to maintain the validity of an existing TAN? | Reconsent for the purpose of maintaining the validity of an existing TAN is not required. | Reconsent for the purpose of maintaining the validity of an existing TAN is not required. | No. | | What is the TAN activation schedule? | TANs are activated and available for use in money movement immediately after generation. | PNC uses a batch activation schedule for TANs. Therefore, TANs are activated approximately 15-30 minutes post generation. Mastercard recommends waiting for 45 minutes after the TAN is generated before attempting money movement with PNC TANs. | ACH payments: May take between 15 to 35 minutes for activation. RTP/FedNow payments: Available immediately. | | How is a TAN revoked? | When the user explicitly revokes data sharing consent, or if the `customerId` or `institutionLoginId` is deleted from the Mastercard Open Finance database. If the TAN has been revoked, the user must reconsent to receive a new TAN. | PNC TANs are only valid if the user's data sharing authorization is valid. Any revocation or expiry of data sharing authorization will revoke a TAN. This includes when a `customerId` or `institutionLoginId` is deleted. PNC may operationally revoke a TAN for reasons including end user request or account fraud concerns. If the TAN has been revoked, the user must reconsent to receive a new TAN. | TANs are only revoked when fraud is detected/reported. Revocation by customers is not currently supported (US Bank may add this in future). If data sharing is revoked, expired, or broken, the TAN remains active if in good standing. | | Is there a way to know if a TAN is valid? | An `aggregationStatusCode` of "947" indicates that a token has been revoked. Accounts with an `aggregationStatusCode` of "0" can be assumed to have valid TANs as this status code indicates that the token has not been revoked. | An `aggregationStatusCode` of "947" indicates a token has been revoked. Accounts with an `aggregationStatusCode` of "0" can be assumed to have valid TANs as this status code indicates that the token has not been revoked. | This will be added in 2026, but given limited revocation of TANs at US Bank, this should not be an issue in the intermediate term. | | Are customers issued a new TAN if consent sharing was revoked but is later reauthorized? | Yes. Chase will issue a new TAN if consent was explicitly revoked and the user later reauthorized. Conversely, Chase will reissue the existing (same) TAN if the data sharing token expired due to non-usage and the user later reauthorized sharing. This occurs because token expiration does not lead to TAN revocation. | Yes. PNC will issue a new TAN if consent was explicitly revoked and the user later reauthorizes data sharing (and the 45-minute window has passed). If a TAN is operationally revoked by PNC (see **"How is a TAN revoked?"**), a new TAN will be issued once the customer reauthorizes. | If a customer has their account TAN revoked for a fraud use case, and they choose to re-authorize data sharing, a new TAN will be issued. | | What is the best practice for keeping TANs valid? | Educating the end user to avoid proactive consent revocation within their account portal is essential for TAN validity. | Once issued and activated, TANs will remain valid unless the `customerId` or `institutionLoginId` are deleted from the Mastercard Open Finance production platform or operationally revoked by PNC (see **"How is a TAN revoked?"**). | No actions are required by data recipients to keep TANs valid for US Bank. | ## Legacy Endpoint {#legacy-endpoint} #### Get Account ACH Details (To be Deprecated) {#get-account-ach-details-to-be-deprecated} This is a historical version of the Get Account ACH Details endpoint; new features and enhancements are being added to the [Get Account ACH Details with RTP/FedNow](https://developer.mastercard.com/open-finance-us/documentation/products/pay/verification-money-transfer/index.md#api) endpoint. API Reference: `GET /aggregation/v1/customers/{customerId}/accounts/{accountId}/details`