Exchange authorized payment methods
Turns an authorization token from a bank login into stored payment methods on the company itself. Every account the login authorized is tokenized with the payment processor and saved as an ach payment method. Requires the payment_methods:write permission.
Authorization
AuthorizationstringrequiredBody
application/json
The authorization token the bank login produced.
tokenstringrequiredThe provider-level authorization token — with Plaid, the public_token its onSuccess callback gives you. Between 1 and 500 characters. Its format is the provider's; treat it as opaque.
Response
200 · The payment methods created from the token.
paymentMethodsPaymentMethod[]requiredThe payment methods that were created. One bank login can authorize several accounts, so this may hold more than one. Accounts already on file are skipped rather than duplicated, so the array can be shorter than the number of accounts authorized, and can be empty.
400 · `token` is missing, empty, or longer than 500 characters.
401 · The request carried no valid access token.
403 · The token is not a property manager token, or it lacks the `payment_methods:write` permission.
422 · The token was accepted by the provider but resolved to no bank accounts.
500 · The payment processor rejected the call — it could not resolve the authorization token, or could not tokenize one of the accounts behind it. The `detail` member carries a summary that is safe to show a user; the provider's own diagnostic text is not returned.
MagicDoor does not issue this token. Call Start payment method setup with mode: "bankAuth", run the returned publicToken through the provider's client-side SDK, let the account holder sign in to their bank, and send back the token the SDK gives you when it finishes.