IP addresses outside of the United States are normally not permissible, so any requests for non-US IPs will require additional scrutiny and will be manually investigated and approved. Any request from a non-whitelisted IP address will return a 403 Forbidden error. Do not share them in public areas, use them in client-side code, or otherwise use them in a way that may compromise their security.Īll requests must come from a whitelisted IP address, which is configured via the client dashboard. Nevertheless, there is an example of Base64 encoding to the right.īecause the values described above may grant access to some or all of your data, you must keep them secret and keep them safe. For instance, all cURL example requests in this documentation use the -u option, e.g., -u 'client_id:api_key'. Technically, basic access authorization requires the Base64 encoding of these values separated by a colon, but many HTTP clients will handle the encoding for you. These values are available on the client dashboard. Requests also require basic access authentication where your client_id is the username and your api_key is the password. MX Platform API requests must use HTTPS with TLSv1.2 encryption or higher or else they will fail. Each transaction belongs to only one account. For instance, a user may have both a checking and savings account associated with one Chase login and would therefore have two accounts associated with that member.Ī transaction represents any instance in which money moves into or out of an account, such as a purchase at a business, a payroll deposit, a transfer from one account to another, an ATM withdrawal, etc. A member may have more than one account associated with it. Aggregation, verification, and many other processes are centered around a member, meaning this is probably the most important type of object you’ll be working with.Īn account represents a financial account held by an FI, e.g., a user’s checking or savings account. A user may have multiple members, one each for their bank, their mortgage broker, their credit card provider, etc. This is because, for example, the mortgage division of Wells Fargo might use a separate system than its everyday banking division, which is different from its credit card division, etc.Ī user represents an end-user accessing the MX Platform API via your application, be it a mobile app, web app, desktop app, etc.Ī member represents the relationship between a user and an institution. It’s important to point out that many real-world FI will actually have several different institution objects within the MX Platform API. OAuth 2 Access Token Authentication (Client Credentials)Īn institution represents a financial institution (FI) like Chase or Wells Fargo.List account statements available for a member.(Deprecated) Request a Payment Processor Access Token.(Deprecated) Request a Payment Processor Authorization Code.Read a category by user (includes custom categories).Member connected, primary action selected.API architecture and resource structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |