Skip to main content

​
New Features

​
Forwarding Requests: Entity Bindings

The Forwarding Requests API now supports entity as a binding type. Previously, the bindings object only accepted payment_instrument and secret resource IDs. You can now bind an Entity and reference its data in your forwarding request templates using the {{entity.field}} syntax. This enables use cases where an individual’s first and last name need to be forwarded to third-party services alongside the associated account number, without exposing raw PII to your system.
Sample Request
{
  "bindings": {
    "payment_instrument": "pmt_inst_7TNTTRQwQxWc",
    "secret": "sec_au22b1fbFrmfp",
    "entity": "ent_au22b1FBFJbp8"
  },
  "url": "https://sample-url/v1/tokens",
  "method": "POST",
  "headers": {
    "Content-Type": "application/json",
    "Authorization": "Bearer {{secret.value}}"
  },
  "body": "{\"first_name\":\"{{entity.individual.first_name}}\",\"last_name\":\"{{entity.individual.last_name}}\",\"number\":\"{{payment_instrument.card.number}}\"}"
}
For more information, visit the Forwarding Requests API documentation.

​
Credit Score Simulations

The Simulate API now supports direct event creation for Credit Score simulations.
  • New endpoint: POST /simulate/events with type set to credit_score.increased or credit_score.decreased
  • This endpoint allows developers to trigger credit score change events for an Entity with an active Credit Score subscription in the development environment, streamlining the testing of credit score-driven workflows
This API is available in the development environment only.
For more information, visit the Simulations API documentation.

​
Improvements

​
Updates API

Student Loan — Opened At The Updates API now surfaces the opened_at field for student_loan liability accounts when source is direct. This field returns the date the student loan was originally opened, providing additional context for loan lifecycle analysis, refinance eligibility assessments, and portfolio segmentation. For more information, visit the Updates API documentation.

​
Webhooks

New Account Surfaced Event A new webhook event, entity.new_accounts_pending_consent, is now fired if a previously undiscovered liability account is surfaced after the user progresses through Connect. This allows your application to be notified in real time when new liability accounts appear on a user’s credit report, enabling you to surface that account to the user for consent without requiring you to poll the Accounts API. For more information, visit the Webhooks API documentation.

​
Connect API

Filter Accounts by Product You can now filter accounts by product type when using Connect. This allows you to scope a Connect session to only surface accounts relevant to a specific product (e.g., only accounts eligible for payments or only accounts with update subscriptions), reducing noise and improving the end-user experience in targeted workflows. For more information, visit the Connect API documentation.

​
Payment Instruments API

Card Billing Zip Code A new billing_zip_code field is now available on card type Payment Instruments. This field is returned as part of the card object when retrieving a Payment Instrument.
  • card.billing_zip_code: The billing zip code associated with the card
This addition supports address verification (AVS) workflows and reduces payment failures caused by billing address mismatches when forwarding card details to third-party processors. For more information, visit the Payment Instruments API documentation.

​
Payments API

Inbound ACH/Wire Trace Numbers & Metadata Inbound ACH and wire payments received via inbound_achwire_payment Payment Instruments now include trace number and metadata fields on the Payment object.
  • source_trace_id: enables end-to-end payment tracking and reconciliation for inbound transfers
  • destination_trace_id: provides the underlying bank transaction ID on the destination Account for outbound reconciliation
  • metadata: allows clients to associate custom reference information with incoming transactions (e.g., you can now add internal reference IDs, ​​customer IDs, and notes in the metadata)
For more information, see the Payments API documentation.