The Bank Account Starter API product introduces to the DevExchange platform the ability to add an account-opening feature to your website or application. We know that your customers have different saving needs (and balances), so we have two great options for them to choose from: 360 Savings and 360 Money Market. Both accounts include the Capital One features you know and love:
No fees — That’s right! No. Fees. Your customers can put their money to work growing and earning.
High interest rates — Among the nation’s best! Your customers can choose the account that works for their balance and their timeline. Saving for specific, small goals (less than $10,000)? 360 Savings Accounts are their best bet. Large deposit ready to go? 360 Money Market Accounts offer higher interest rates than 360 Savings Accounts do for balances over $10,000.
No minimum balance — Don’t wait to start seeing your savings grow! Both accounts can be opened with only a penny to fund.
A robust set of tools that can help your users track progress toward specific savings goals — No matter what they’re saving for, your customers can see their path and follow it.
Which one to choose? For smaller goals with quicker target dates - say, an account you can open as part of a wedding registry or travel site - 360 Savings makes the most sense; for larger goals with less definite end dates - savings for a home down payment or a rainy day fund - 360 Money Market can provide a higher return. And future releases will add even more account options.
Use the Bank Account Starter API to do more than just advise your end users to save; point them directly to some of the best savings vehicles in the industry, and allow them to open an account now. It’s a win for everyone!
The Credit Offers API provides tools that you can use to offer Capital One credit products to your customers. To integrate with these tools, you must be a Capital One affiliate.
For information about becoming an affiliate, and for details about how to get your client application approved, see the Affiliate Playbook.
The following resources are available:
Product Listings provides a comprehensive list of Capital One credit products that you can offer to your customers, based on your affiliate status.
Prequalifications lets your customers request a list of credit products for which they may be eligible. Requesting this list does not affect the applicant’s credit score, but it also does not guarantee that an actual application for any of the returned credit products will be successful. For more information, see What does being pre-qualified mean?
This API includes an endpoint that you must call to acknowledge that the prequalification results were received and displayed to your customers. This call must be made within 20 minutes of receiving the results; failure to do so can result in the termination of your API credentials.
An additional Prequalifications Summary resource lets you examine summary statistics for some or all of the prequalification checks that your customers have submitted.
A key feature of most Capital One credit cards is the associated loyalty, or Rewards, program. This program grants loyalty bonuses — generically referred to as rewards, but issued as miles, cash back, or points — based on card usage. Rewards are collected in and redeemed from a rewards account that is associated with the credit card account but exists as a separate entity.
Capital One supports a wide variety of rewards programs, each of which defines its own set of operational rules. What they all have in common are the three basic elements:
the rewards currency — a rewards account accumulates value measured in a specific kind of currency: miles (for travel-related rewards), points, or cash back.
Miles and points are converted to a cash value for redemption; cash back is just that — dollars and cents.
the earn rate — credit card customers earn rewards based on purchases they make using the associated credit card; these earn rates vary both across programs and within a single program based on a number of factors.
the redemption opportunities — once accumulated, rewards can then be redeemed: exchanged for a new purchase, used to erase a previous purchase, donated to a charitable organization, or just received as cash. Again, the available options vary both across programs and within a single program.
You can use the Rewards API Product to get the details that determine how a specific rewards program works. The endpoints currently available allow you to obtain a list of all rewards accounts associated with a named customer, and to obtain a set of details about a specific rewards account (including balance, currency, and the available redemption opportunities).
And we’ve designed these APIs to keep our customer data secure: account owners must grant you permission to access their accounts, and all authentication and authorization is handled by Capital One.
The Rewards API Product is your ticket to a new way to provide value for your customers — by helping them access the value of their rewards.
SwiftID? provides strong two-factor authentication for Capital One customers by allowing them to use their registered mobile devices for identity verification.
The SwiftID API lets you integrate your application with this extra layer of security. It works by sending a SwiftID request — a task — to your customers who have set up SwiftID. The task asks them to approve or deny requests to access the personal information or protected resources that you manage on their behalf. You can also use SwiftID to provide enhanced security at login. The API lets your customers more easily and securely approve access to resources, and you can protect their information more securely.
Task status is provided by a webhook notification call to your registered callback URL. You must register a callback URL prior to creating a task. See the reference documentation for details on creating webhooks and SwiftID tasks.
SwiftID integration provides the following operations:
Create SwiftID task (POST /identity/enhanced-authentication/tasks) lets you send a request for a SwiftID approval to a customer’s registered mobile device
Create Webhook (POST /identity/webhooks) lets you register a callback URL to receive the status of the SwiftID task
Retrieve Webhooks (GET /identity/webhooks) lets you get the complete list of callback URLs that you registered as webhooks
Retrieve Webhook (GET /identity/webhooks/{webhookId}) lets you get the details of a specified callback URL
Update Webhook (PUT /identity/webhooks/{webhookId}) lets you update the callback URL for a specified callback URL
Delete Webhook (DELETE /identity/webhooks/{webhookId}) lets you delete a specified callback URL