Invoices
Checks the method type to be used for membership payments Fees will be added to the Invoices in Oracle AR where needed
| API | Description |
|---|---|
| POST api/invoices/methods |
Invoices with their method types will be returned |
FBC Payments Utility API
Current Version: 2.8.0.0
Description: This API supports the FBC Member payment method type lookup for Oracle Financials.
API Support:
MyEzPay, Inc.
844-MYEZPAY (693-9729)
helpdesk@myezpay.com
https://fbcsupport.myezpay.com
Endpoints
All requests to the FBC Payments API are sent via HTTP POST, GET, and DELETE methods to one of our API endpoint URLs.
Sandbox API Endpoint: https://utilitydev.fbcpayments.com/api/
Production API Endpoint: https://utility.fbcpayments.com/api/
Sample Call: https://utilitydev.fbcpayments.com/api/invoices/methods (POST)
XML Content-Type: text/xml
JSON Content-Type: application/json
Authorization
The FBC Utility API requires a custom header to authenticate all calls.
X-APIKey: F263FAQW3WZ7UBZMRFI0GX3Y9QBGVVM3RK9LH946 (Key/Value Pair)
Note: This is a sample key. MyEzPay will issue live keys for each active Club in the system.
Response
Contains the server response data from the API call. All responses from the API will contain an http header. Use the httpcode and status elements to troubleshoot errors.
Response Data Fields
| Element | Description | Type |
|---|---|---|
| Success | Returns true if the call was a success | boolean |
| HttpCode | The Http Status Code from the response | string |
| HttpStatus | The Http Status Title from the response | string |
| Message | The Status Message from the response | string |
| Data |
Conditional - Only included on specific calls The specific data returned in the call |
JSON Object |
Response Status Codes
These codes will be returned in the header of all responses for troubleshooting the API calls to the server. The data section of the JSON response will contain information and codes relating to the specific function that was called.
200 - Client Authorized
The API Call was properly formatted, authenticated, received, and processed by the server.
400 - Bad Request
Some Required Fields were missing in the request. Check your form data and try again.
401 - Not Authorized
Invalid API Key was used, check the value of the Key you used and contact MyEzPay support if you still get this message.
500 - Internal Server Error
A server or connectivity error has occurred. Wait for the service to come back online and try your request again. Contact MyEzPay support if still get error messages. Please include the error message you are receiving.