<user_uuid>
, which refers to the unique identifier of the registered business or individual that was obtained from the registration API.
Billing
GrailPay’s API supports associating specific billable events with a particular merchant, enabling precise attribution for billing purposes. This feature allows you to link the UUID of a user tied to a merchant (a business that has undergone KYB verification) to the billing event recorded for the API call. To attribute the billing event to a merchant, include the following parameter in your request payload:- billing_merchant_user_uuid: The unique identifier (UUID) of the user associated with the merchant to whom this billable event should be attributed.
Endpoint
POST /3p/api/v1/bank-account/{user_uuid}Request Payload
Fields | Type | Is Required | Description |
---|---|---|---|
billing_merchant_user_uuid | string | No | The UUID of the user associated with the merchant that should be associated with the billable event that is created when onboarding a new perso |
plaid.access_token | string | Plaid user access token | |
plaid.account_id | string | Plaid user account id | |
custom.account_number | string | Bank account number maximum of 17 characters | |
custom.routing_number | string | Bank account routing number 9-digit ABA routing transit number associated with the account | |
custom.account_name | string | Name of account in bank | |
custom.account_type | string | Bank account type Possible values: savings checking |
Response Object
Errors & Warnings
Code | Reason | Message |
---|---|---|
401 | ||
403 | ||
406 | Invalid Billing Merchant User UUID | The requested billing merchant user uuid does not exist. |
406 | Billing Merchant has been deleted | The billing merchant is deleted and cannot be used for billing purposes. |
422 |