# Netevia ## Docs - [Add a new bank account for a user ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/bank-accounts/add-a-new-bank-account-for-a-user-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Add a new bank account to a person. ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/add-a-new-bank-account-to-a-person-stable-.md): This endpoint allows for adding a new Bank Account to the GrailPay ACH API Ecosystem. The only item that is required is the Bank Account object. When including the bank account, you can pass either Plaid information or account and routing information. You should never pass both. - [Add bank account. ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/bank-accounts/add-bank-account-sunsetting-.md): Add a bank account for a specific user. **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Delete a bank account ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/delete-a-bank-account-stable-.md): Deletes a bank account by its UUID and aggregator type. - [Fetch the bank account balance ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/fetch-the-bank-account-balance-stable-.md): Fetch the balance of a specific bank account for a user. - [Fetch the transaction history for a bank account. ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/fetch-the-transaction-history-for-a-bank-account-stable-.md): Fetch a list of transactions for a bank account. This currently only works with accounts linked through the Bank Link SDK. - [Get all bank accounts for a user ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/get-all-bank-accounts-for-a-user-stable-.md): This API retrieves a list of all bank accounts associated with a business or person. The response includes details such as the account number, routing number, account holder's name, account type, and other relevant information. - [Get all bank accounts for a user ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/bank-accounts/get-all-bank-accounts-for-a-user-sunsetting-.md): This API retrieves a list of all bank accounts associated with a business or person. The response includes details such as the account number, routing number, account holder's name, account type, and other relevant information. **This Endpoint is Sunsetting and you should use the stable endpoint.… - [Get balance approval ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/get-balance-approval-stable-.md): Retrieve the balance approval for a specific user. - [Get bank account details ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/get-bank-account-details-stable-.md): Retrieve the bank account details for a specific user. - [Get User Details by bank account ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/get-user-details-by-bank-account-stable-.md): This API will return the details of the user associated with a specific bank account - [Switch default bank account ( STABLE )](https://docs.ach.netevia.com/api-reference/bank-accounts/switch-default-bank-account-stable-.md): Switch default bank account - [Validate bank account and routing number ( STABLE ) ](https://docs.ach.netevia.com/api-reference/bank-accounts/validate-bank-account-and-routing-number-stable-.md): GrailPay provides a standalone Account and Routing Number Validation API, allowing businesses to verify bank account details before onboarding an entity or processing transactions. Using this validation helps prevent failed transactions, failed payouts, and other payment issues by ensuring that the… - [Get Billing by Merchant User UUID ( STABLE )](https://docs.ach.netevia.com/api-reference/billing/get-billing-by-merchant-user-uuid-stable-.md): This retrieves a summary of all billed events for a specific merchant, providing comprehensive billing details to support seamless integration. - [Fetch a Batch Payout ( Processor Only ) ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/payouts/fetch-a-batch-payout-processor-only--sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Get All Batch Payouts ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/payouts/get-all-batch-payouts-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** This API retrieves a list of all batch payouts. The response provides details for each payout, including the total amount and relevant timestamps. Paginati… - [Get Batch Merchant Payout ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/payouts/get-batch-merchant-payout-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.**GrailPay enables merchants to receive a single batch payout per day, consolidating multiple transactions into one payout instead of processing individual tr… - [Get Batch Payout ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/payouts/get-batch-payout-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** This API retrieves the details of a specific batch payout using its unique batch payout UUID. The response provides comprehensive information about the pay… - [Get Business Batch Payout ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/get-business-batch-payout-stable-.md): This API retrieves the details of a business batch payout using the business user UUID and the unique batch payout UUID. The response provides comprehensive information about the payout, including the total amount and a detailed breakdown of the transactions. - [Get Merchant Batch Payout ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/get-merchant-batch-payout-stable-.md): This API retrieves the details of a merchant batch payout using the merchant user UUID and the unique batch payout UUID. The response provides comprehensive information about the payout, including the total amount and a detailed breakdown of the transactions. - [Get Person Batch Payout ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/get-person-batch-payout-stable-.md): This API retrieves the details of a person batch payout using the person user UUID and the unique batch payout UUID. The response provides comprehensive information about the payout, including the total amount and a detailed breakdown of the transactions. - [Get Processor Batch Payout ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/get-processor-batch-payout-stable-.md): This API retrieves the details of a processor batch payout using the unique batch payout UUID. The response provides comprehensive information about the payout, including the total amount and a detailed breakdown of the transactions. - [List Business Batch Payouts ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/list-business-batch-payouts-stable-.md): This API retrieves all business batch payouts associated with the business user UUID. The response provides comprehensive details about each payout, including the total amount and detailed information for each payout. - [List Merchant Batch Payouts ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/list-merchant-batch-payouts-stable-.md): This API retrieves all merchant batch payouts associated with the merchant user UUID. The response provides comprehensive details about each payout, including the total amount and detailed information for each individual payout. - [List Person Batch Payouts ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/list-person-batch-payouts-stable-.md): This API retrieves all person batch payouts associated with the person user UUID. The response provides comprehensive details about each payout, including the total amount and detailed information for each payout. - [List Processor Batch Payouts ( STABLE )](https://docs.ach.netevia.com/api-reference/payouts/list-processor-batch-payouts-stable-.md): This API retrieves all batch payouts associated with the processor. The response provides comprehensive details for each payout, including the total amount and specific information for each payout. - [Get All Batch Refunds ( STABLE )](https://docs.ach.netevia.com/api-reference/refunds/get-all-batch-refunds-stable-.md): This API retrieves a list of all batch refunds. The response provides details for each batch refund, including the total amount and relevant timestamps. Pagination options are available to efficiently manage large datasets. - [Get Batch Refund ( STABLE )](https://docs.ach.netevia.com/api-reference/refunds/get-batch-refund-stable-.md): This API retrieves the details of a specific batch refund using its unique batch refund UUID. The response provides comprehensive information about the refund, including the total amount and the associated transactions. - [Get Batch Refund ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/refunds/get-batch-refund-sunsetting-.md): This API is processor specific and returns a list of refunds included in the specified batch. **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Get Refund Details ( Refunds )](https://docs.ach.netevia.com/api-reference/refunds/get-refund-details-refunds-.md): This API returns the details of a refund request. - [Get Transaction Refunds ( STABLE )](https://docs.ach.netevia.com/api-reference/refunds/get-transaction-refunds-stable-.md): This API returns a list of refund requests for a specific transaction. - [Refund a transaction ( STABLE )](https://docs.ach.netevia.com/api-reference/refunds/refund-a-transaction-stable-.md): Once a transaction has been completed, this API can be used to issue a refund, thereby clawing back funds from the payee and transferring them back to the payor. An optional amount can be specified to either issue a partial refund or add additional fees to the original amount. If the amount is not s… - [Cancel a transaction in the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/transactions/cancel-a-transaction-in-the-ach-application-stable-.md): This endpoint allows to cancel a transaction in the GrailPay ACH API Ecosystem. - [Cancel a transaction ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/transactions/cancel-a-transaction-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Cancel a transaction ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/transactions/cancel-a-transaction-sunsetting--1.md): A transaction can only be canceled while in the CAPTURE_PENDING state. You can no longer cancel a transaction after the ACH capture process has begun. **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Create a new transaction ( STABLE )](https://docs.ach.netevia.com/api-reference/transactions/create-a-new-transaction-stable-.md): Once authenticated, the client application can send a request to create a new transaction by providing relevant details such as the payment amount, sender and receiver. GrailPay will then return a UUID, which serves as the unique identifier and can be used to fetch the details and status of the tran… - [Get Transaction by UUID ( STABLE )](https://docs.ach.netevia.com/api-reference/transactions/get-transaction-by-uuid-stable-.md): When making a request to an API for a transaction's information, you typically need to provide a unique identifier UUID. The UUID is generated at the time of creating a transaction and is associated with the each transaction. - [Get Transaction by UUID ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/transactions/get-transaction-by-uuid-sunsetting-.md): When making a request to an API for a transaction's information, you typically need to provide a unique identifier UUID. The UUID is generated at the time of creating a transaction and is associated with the each transaction. **This Endpoint is Sunsetting and you should use the stable endpoint. Su… - [Get Transaction List ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/transactions/get-transaction-list-sunsetting-.md): Get a list of transactions. **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Get Transactions ( STABLE )](https://docs.ach.netevia.com/api-reference/transactions/get-transactions-stable-.md): Retrieve a list of transactions based on filter parameters - [Pause a transaction in the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/transactions/pause-a-transaction-in-the-ach-application-stable-.md): This endpoint allows to pause a transaction in the GrailPay ACH API Ecosystem. - [Resume a transaction in the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/transactions/resume-a-transaction-in-the-ach-application-stable-.md): This endpoint allows to resume a paused transaction in the GrailPay ACH API Ecosystem. - [Deleting a User ( STABLE )](https://docs.ach.netevia.com/api-reference/users/deleting-a-user-stable-.md): This API deletes a specific user from the system based on their unique user UUID. - [Get All Businesses ( STABLE )](https://docs.ach.netevia.com/api-reference/users/get-all-businesses-stable-.md): This endpoint provides a comprehensive list of all registered businesses, including essential details. Pagination options are available to efficiently manage large datasets. - [Get All Merchants ( STABLE )](https://docs.ach.netevia.com/api-reference/users/get-all-merchants-stable-.md): This endpoint provides a comprehensive list of all registered merchants, including essential details. Pagination options are available to efficiently manage large datasets. - [Get All People ( STABLE )](https://docs.ach.netevia.com/api-reference/users/get-all-people-stable-.md): This endpoint provides a comprehensive list of all registered people, including essential details. Pagination options are available to efficiently manage large datasets. - [Get All Users ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/users/get-all-users-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Get Business ( STABLE )](https://docs.ach.netevia.com/api-reference/users/get-business-stable-.md): This endpoint will return detail of the business. When making a request to an API for a business's information, you typically need to provide a unique identifier UUID. The UUID is generated at the time of registration and is associated with the business's account. - [Get Merchant ( STABLE )](https://docs.ach.netevia.com/api-reference/users/get-merchant-stable-.md): This endpoint will return detail of the merchant. When making a request to an API for a merchant's information, you typically need to provide a unique identifier UUID. The UUID is generated at the time of registration and is associated with the merchant's account. - [Get Person ( STABLE )](https://docs.ach.netevia.com/api-reference/users/get-person-stable-.md): This endpoint will return detail of the person. When making a request to an API for a person's information, you typically need to provide a unique identifier UUID. The UUID is generated at the time of registration and is associated with the person's account. - [Get User ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/users/get-user-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Onboard a new Business into the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/users/onboard-a-new-business-into-the-ach-application-stable-.md): This endpoint allows for adding a new Business to the GrailPay ACH API Ecosystem. The only item that is required is the Bank Account object, but we strongly encourage that you supply as much information as possible. When including the bank account, you can pass either Plaid information or account… - [Onboard a new Business or Merchant into the ACH application ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/users/onboard-a-new-business-or-merchant-into-the-ach-application-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Onboard a new Merchant into the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/users/onboard-a-new-merchant-into-the-ach-application-stable-.md): This endpoint allows for adding a new Merchant to the GrailPay ACH API Ecosystem. - [Onboard a new person ( DEPRECATED )](https://docs.ach.netevia.com/api-reference/users/onboard-a-new-person-deprecated-.md): **This Endpoint is deprecated. Deprecated APIs that are no longer supported and should be removed from your integration. Please use the Stable version for your integration.* - [Onboard a new Person into the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/users/onboard-a-new-person-into-the-ach-application-stable-.md): This endpoint allows for adding a new Person to the GrailPay ACH API Ecosystem. The only item that is required is the Bank Account object, but we strongly encourage that you supply as much information as possible. When including the bank account, you can pass either Plaid information or account an… - [Onboard a new Person into the ACH application ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/users/onboard-a-new-person-into-the-ach-application-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [Register a new business ( DEPRECATED )](https://docs.ach.netevia.com/api-reference/users/register-a-new-business-deprecated-.md): **This Endpoint is deprecated. Deprecated APIs that are no longer supported and should be removed from your integration. Please use the Stable version for your integration.** - [Update a Business into the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/users/update-a-business-into-the-ach-application-stable-.md): This endpoint allows for updating a Business to the GrailPay ACH API Ecosystem. - [Update a Merchant into the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/users/update-a-merchant-into-the-ach-application-stable-.md): This endpoint allows for updating a Merchant to the GrailPay ACH API Ecosystem. - [Update a Person into the ACH application ( STABLE )](https://docs.ach.netevia.com/api-reference/users/update-a-person-into-the-ach-application-stable-.md): This endpoint allows for updating a Person to the GrailPay ACH API Ecosystem. - [Update Business KYB ( DEPRECATED )](https://docs.ach.netevia.com/api-reference/users/update-business-kyb-deprecated-.md): **This Endpoint is deprecated. Deprecated APIs that are no longer supported and should be removed from your integration. Please use the Stable version for your integration.** - [Update Business KYB ( SUNSETTING )](https://docs.ach.netevia.com/api-reference/users/update-business-kyb-sunsetting-.md): **This Endpoint is Sunsetting and you should use the stable endpoint. Sunsetting APIs that are still supported but scheduled for deprecation.** - [De-register Processor Webhook ( DEPRECATED )](https://docs.ach.netevia.com/api-reference/webhooks/de-register-processor-webhook-deprecated-.md): *This Endpoint is deprecated. Deprecated APIs that are no longer supported and should be removed from your integration. Please use the Stable version for your integration.** Once deregistered, the previously registered webhook will no longer be triggered by the GrailPay, and notifications will no l… - [De-register Webhook ( STABLE )](https://docs.ach.netevia.com/api-reference/webhooks/de-register-webhook-stable-.md): Deregistering a webhook via API involves removing a previously registered webhook configuration from the GrailPay. To disable notification related to particular transaction events, you need to de-register webhook with registered events name. - [Get registered processor webhooks ( DEPRECATED )](https://docs.ach.netevia.com/api-reference/webhooks/get-registered-processor-webhooks-deprecated-.md): *This Endpoint is deprecated. Deprecated APIs that are no longer supported and should be removed from your integration. Please use the Stable version for your integration.** Retrieve a list of registered webhooks for the authenticated user. - [Get registered webhooks ( STABLE )](https://docs.ach.netevia.com/api-reference/webhooks/get-registered-webhooks-stable-.md): Retrieve a list of registered webhooks for the authenticated user. - [Register Processor Webhook ( DEPRECATED )](https://docs.ach.netevia.com/api-reference/webhooks/register-processor-webhook-deprecated-.md): *This Endpoint is deprecated. Deprecated APIs that are no longer supported and should be removed from your integration. Please use the Stable version for your integration.** Once registered, the webhook will be triggered by the GrailPay whenever a relevant event occurs, such as a transaction starte… - [Register Webhook ( STABLE )](https://docs.ach.netevia.com/api-reference/webhooks/register-webhook-stable-.md): Registering a webhook via API call involves configuring a client application to receive notifications and updates from GrailPay. To enable notification related to transaction, you need to register webhook with sets of predefined Events. - [Changelog](https://docs.ach.netevia.com/changelog/changelog.md) - [Account Intelligence Setup Guide](https://docs.ach.netevia.com/docs/business/account-intelligence-setup-guide.md) - [ACH Setup Guide](https://docs.ach.netevia.com/docs/business/ach-setup-guide.md): This guide details how to get your ACH program started, and includes additional information about the expected behavior of ACH payments, which often differs from other common payment methods, like credit cards. - [Overview](https://docs.ach.netevia.com/docs/business/overview.md) - [Key Terms](https://docs.ach.netevia.com/docs/business/resources/key-terms.md) - [Return Codes](https://docs.ach.netevia.com/docs/business/resources/return-codes.md) - [Authentication](https://docs.ach.netevia.com/docs/technical/authentication.md) - [Add Bank Account](https://docs.ach.netevia.com/docs/technical/bank-accounts/add-bank-account.md): Suggest Edits - [Delete Bank Account](https://docs.ach.netevia.com/docs/technical/bank-accounts/delete-bank-account.md): Delete the existing bank account - [Fetch Bank Account](https://docs.ach.netevia.com/docs/technical/bank-accounts/fetch-bank-account.md): Suggest Edits - [Get Account Balance](https://docs.ach.netevia.com/docs/technical/bank-accounts/get-account-balance.md): Suggest Edits - [Get All Bank Accounts](https://docs.ach.netevia.com/docs/technical/bank-accounts/get-all-bank-accounts.md): Suggest Edits - [Get User by Bank Account](https://docs.ach.netevia.com/docs/technical/bank-accounts/get-user-by-bank-account.md): Suggest Edits - [Set Default Account](https://docs.ach.netevia.com/docs/technical/bank-accounts/set-default-account.md): This API sets the default bank account for a specific user. The default account is used in transactions when no account is specified. - [Validate Account & Routing Number](https://docs.ach.netevia.com/docs/technical/bank-accounts/validate-account-and-routing-number.md): A stand alone endpoint that allows for account and routing number validation. - [Get Merchant Billing Summary](https://docs.ach.netevia.com/docs/technical/billing/get-billing-items-by-business.md): Fetch a summary of billed events for a merchant. - [Transaction Scenarios - Batch Payout](https://docs.ach.netevia.com/docs/technical/example-transaction-batch-payout-scenarios.md): A description of the different transaction scenarios that can occur when using batch payouts. - [Transaction Scenarios - Direct Payouts](https://docs.ach.netevia.com/docs/technical/example-transaction-direct-payout-scenarios.md): A description of the different transaction scenarios that can occur when using direct payouts. - [Idempotency](https://docs.ach.netevia.com/docs/technical/idempotency.md) - [Overview](https://docs.ach.netevia.com/docs/technical/overview.md) - [Get All Batch Payouts](https://docs.ach.netevia.com/docs/technical/payouts/get-all-batch-payouts.md): An API endpoint for retrieving all batch payouts - [Batch Merchant Payout](https://docs.ach.netevia.com/docs/technical/payouts/get-batch-merchant-payout.md): An API endpoint that fetches a batch payout for a merchant - [Batch Payout](https://docs.ach.netevia.com/docs/technical/payouts/get-batch-payout.md): An api endpoint for retrieving a batch payout - [Get All Batch Refunds](https://docs.ach.netevia.com/docs/technical/refunds/get-all-batch-refunds.md): Suggest Edits - [Get Batch Refund](https://docs.ach.netevia.com/docs/technical/refunds/get-batch-refund.md): Suggest Edits - [Get Refund Details](https://docs.ach.netevia.com/docs/technical/refunds/get-refund-details.md): Suggest Edits - [Get Transaction Refunds](https://docs.ach.netevia.com/docs/technical/refunds/get-transaction-refunds.md): Suggest Edits - [Refund a Transaction](https://docs.ach.netevia.com/docs/technical/refunds/refund-a-transaction.md): An API endpoint for issuing refunds on transactions. - [Sandbox](https://docs.ach.netevia.com/docs/technical/sandbox-environment.md) - [Transactions Overview](https://docs.ach.netevia.com/docs/technical/transactions-overview.md) - [Cancel a Transaction](https://docs.ach.netevia.com/docs/technical/transactions/cancel-a-transaction.md): A transaction can only be canceled while in the CAPTURE_PENDING state. You can no longer cancel a transaction after the ACH capture process has begun. - [Create a Transaction](https://docs.ach.netevia.com/docs/technical/transactions/create-a-transaction.md): Suggest Edits - [Fetch a Transaction](https://docs.ach.netevia.com/docs/technical/transactions/fetch-a-transaction.md): Suggest Edits - [Get All Transactions](https://docs.ach.netevia.com/docs/technical/transactions/fetch-transaction-list.md): Suggest Edits - [Deleting a User](https://docs.ach.netevia.com/docs/technical/users/delete-user.md): This endpoint allows for the deletion of a user - [Get All Users](https://docs.ach.netevia.com/docs/technical/users/get-all-users.md): This endpoints allow to get all users - [Get User](https://docs.ach.netevia.com/docs/technical/users/get-user.md): This endpoints allow to get the user by user uuid - [Onboarding a Business](https://docs.ach.netevia.com/docs/technical/users/onboard-a-business.md) - [Onboard a Person](https://docs.ach.netevia.com/docs/technical/users/onboard-a-person.md) - [Update KYB](https://docs.ach.netevia.com/docs/technical/users/update-kyb-for-business.md): Suggest Edits - [De-register Webhook](https://docs.ach.netevia.com/docs/technical/webhooks/de-register-webhook.md): Suggest Edits - [Webhook Events](https://docs.ach.netevia.com/docs/technical/webhooks/events.md): Suggest Edits - [Get All Webhook Events](https://docs.ach.netevia.com/docs/technical/webhooks/get-all-webhook-events.md): Suggest Edits - [Register a Webhook](https://docs.ach.netevia.com/docs/technical/webhooks/register-a-webhook.md): Suggest Edits - [Welcome](https://docs.ach.netevia.com/home/welcome.md) ## OpenAPI Specs - [docs?api-docs](https://api.grailpay.com/docs?api-docs.json) - [openapi](https://docs.ach.netevia.com/api-reference/openapi.json) ## Optional - [Blog](https://grailpay.com/in-the-news/) - [FAQ](https://grailpay.com/faq/)