What's new in v0.1?

What's new and what's changed from v0?

Overview

A number of major changes have been made to make it easier to implement Bond's platform and to provide better usability for our customers. Below is a quick summary of the key changes to be aware of in v0.1:

  • In v0.1, the cards API currently only supports secured charge cards. Unsecured credit cards and prepaid cards are still available in v0, and support for these in v0.1 will be released in the near future. Due to these changes to the cards API, cards issued in v0 can't be accessed with v0.1 APIs and vice versa.
  • Plaid linking for external accounts is not present in v0.1; you must use v0 for linking external accounts.
  • You can now create Deposit Accounts and use the v0.1 transfers API for almost all transfers. The only transfers that require the v0 transfers API are those involving linked external accounts.

What's new in v0.1?

  • Secured charge cards
  • Transfers/payments:
    • Secured deposit account to a credit account (repayments)
    • ACH origination from an external account to a secured deposit account
    • ACH origination from an external account to a credit account (repayment)

For details, see User Guide—Transfers and API Reference—Transfers.

  • Account statements:
    • Credit account statements
    • Deposit account statements
    • Secured deposit account statements
  • KYC is now an integral and automatic part of a credit application

What's no longer available?

Transactions

  • /transactions/{transaction_id}/history is not available but may be reintroduced in the future

For details, see User Guide—Transactions and API Reference—Transactions.

Balances

The /balances endpoint has been deprecated and is replaced by the balance object in /accounts. You should now use the /accounts API to check the balance of a card. Because card and card account generation happen concurrently via the POST /cards operation, cards are attached to an account that holds the balance for that card.

For details, see Accounts Overview and Accounts

External accounts

The accounts API now accommodates the new v0.1 accounts model (see accounts) for Deposit Accounts in Bond.

Linking external accounts via API, however, is only supported in v0 at this time. External accounts will be added to v0.1 API in the near future. For details, see User Guide—External accounts.

If you are using the Bond SDK, you will not notice any changes or be required to make any manual changes due to this version update. You can continue with development as usual.

Method changes

API changes

  • Cards re-issue /cards/card_id/reissue
  • Activate card /cards/card_id/activate
  • Close card /cards/card_id/close

PATCH

  • /cards/change_status/{card_id} is now /cards/{card_id}
  • Card status is now part of the PATCH method

PATCH to POST

  • /cards/close/{card_id} is now /cards/{card_id}/close
  • /cards/{card_id}/activate_physical_card is now /cards/{card_id}/activate
  • /cards/reissue/{card_id} is now /cards/{card_id}/reissue

Card field changes

Fields removedRemarks
pseudoDDANumbersobject—no longer needed.
pseudoDdaNumberMoved to account_number on the Accounts resource.
sponsor_bank_routing_numberMoved to routing_number on the Accounts resource.
credit_limitMoved to the Accounts resource.
card_account_idRenamed to account_id
Field addedRemarks
account_idcards now accepts account_id for secured charge cards.

For details, see User Guide—Cards and API Reference—Cards.

Functional changes

account/routing_number

This has been moved to account and is no longer present in cards objects.

For details, see User Guide—Accounts and API Reference—Accounts.

Change card status

/v0/cards/change_status/{card_id} has been deprecated and merged with the /v0.1/cards/{card_id} functionality. You can now PATCH the card status on the card resource.

Credit limit

This has been moved to cards.

cards no longer takes credit_limit as a field. To alter the credit limit of a card, PATCH the credit_limit on accounts.

Create a card

cards now requires account_id and no longer takes program_id. The account_id for v0.1 is the secured_deposit_account_id. More account types will be available in the near future.

Prepaid cards

Prepaid cards require program_id to be created. This functionality currently exists only in v0.

Unsecured credit cards

Unsecured credit cards are supported on the v0 /cards API. We will be extending this soon to v0.1 as we add support for additional account types.

Accounts

The Accounts collection no longer supports external accounts (see v0 documentation). The Accounts collection now creates Accounts objects.

📘

Note

Generating and retrieving linked external accounts requires using the v0 APIs.

The Create an account endpoint creates consumer and commercial Deposit Accounts but does not create secured deposit accounts.

Webhooks

  • Webhook response payload is now contained within the webhook_subscription object:
    • webhook_subscription Object in synchronous responses
    • webhook_subscriptions List in the Get all webhook subscriptions API response
  • status:
    • new enums: STATUS_ENABLED and STATUS_DISABLED
  • New version field allows you to designate the version of the webhook payload Bond sends to your system.
  • Removed action add_events and remove_events. You can now patch the exact events to be configured.
  • events PATCH and POST support wildcards, for example cards.* kyc.*, and so on.
  • The url keyname replaces callback_url

For details, see User Guide—Webhooks and API Reference—Webhooks.