Using Disbursement Data Only

If you already have your own payment rails, or you're looking to graduate to new ones, we've got you covered. You don't have to route payments through Spinwheel to benefit from the data behind them.

Out of the box, we support fetching the proper payee information for the liabilities you're looking to pay — the same verified account, routing, and creditor details that power Direct Pay, just handed to you to execute on your own infrastructure instead.

The Capabilities Matrix Remains Key

Even without submitting a payment through Spinwheel, the capabilities matrix remains your starting point. It tells you, per liability, whether disbursement data is available and payable.

Fetching Disbursement Data

Instead of submitting a payment request, you'll call the disbursement data endpoint to retrieve payee information for a supported liability — account and routing details, creditor identifiers, and anything else your own payment rails need to originate the transaction.

This path is built for two situations in particular:

  • You already run your own payment infrastructure and want verified, current payee data without duplicating a payments stack.
  • You're planning to move off Spinwheel Direct Pay as you scale, and want a clean way to bring payments in-house without losing the data quality you started with.

Either way, the switch between models doesn't lock you out or force a rebuild. It's the same underlying data, just handed off at a different point in the flow.


Did this page help you?