API Reference

BankAccountValidation

API specification for Glomo (1.0.0)

The Glomo API follows REST architecture, utilizing resource-oriented URLs for clarity. It handles form-encoded request bodies, delivers responses in JSON format, and operates with standard HTTP methods, authentication, and response codes.

You can download the complete API collection by using the download options on the right.

Download OpenAPI description

openapi.json

openapi.yaml

Overview

E-mail

developer@glomopay.com

License

Apache 2.0

Servers

Production server

https://api.glomopay.com/api/v1/

Balance

This resource represents your Glomo balance. You can retrieve it to see the current balance on your Glomo account in all currencies enabled for your account.

Operations

Balance Conversions

Balance Conversion resource represents the details of the balance conversion. The balance conversion is the conversion of the balance from one supported currency to another supported currency.

Operations

Payment Link

A payment link is a shareable URL that will take your customers to a Glomo-hosted payment page. The payment page can only be accessed by your customer after the completion of 1FA via their email.

Operations

Orders

This resource represents the order details. The order is the request to receive payment from your customer.

Operations

Customer

This resource represents a customer of your business. The customer can be an individual or a business from whom you will receive payments.

Operations

Document

Document resource represents the documents details uploaded. This document is used in payin, payout, etc.

Operations

Payment

This resource represents a payment attempt made by your customer. The payment can either be successfully completed or failed, depending on various factors.

Operations

Refund

This resource represents a refund transaction from your Glomo account to your customer. You can retrieve it to see the details of the refund transaction.

Operations

Price

This resource represents the pricing details of the payin or payout. The pricing details include the fees and the pricing type

Operations

Subscription

This resource represents a recurring billing agreement for a customer. Subscriptions allow businesses to automatically charge customers on a regular schedule according to a defined billing plan.

Operations

Payout

This resource represents the disbursement transactions from your Glomo account to your beneficiaries.

Operations

Beneficiary

This resource represents a payee of a payout initiated by your business. The beneficiary can be an individual or a business to whom you will send funds.

Operations

Bank Account Validation

Bank Account Validation resource represents the validation details of a bank account.

Operations

BankAccountValidation

idstringread-only

The unique identifier for the bank account validation.

Example: "aval_5JU9yv0lGSUP"

statusstring

The status of the bank account validation. This does not mean the bank account is valid or invalid. It means the validation process was successful or failed.

Enum"success""failed"

validation_messagestring

The message returned by the bank account validation process.

Example: "The account is registered to John Doe"

fee_chargedobject(Money)

The fee charged for the bank account validation process.

{
  "id": "aval_5JU9yv0lGSUP",
  "status": "success",
  "validation_message": "The account is registered to John Doe",
  "fee_charged": {
    "amount": 1000,
    "currency": "USD"
  }
}

Validate any bank account

Request

Security

JWT

Bodyapplication/jsonrequired

One of:

countrystring(iso-3166-1-alpha-3, case-insensitive)required

The country where the customer is located. Country should be sent as a ISO 3166-1 alpha-3 code.

Example: "Ind"

holder_namestringrequired

The name of the account holder.

Example: "John Doe"

account_numberstringrequired

The account number of the bank account as provided by the bank.

Example: "987654321001"

bic_primarystringrequired

The primary BIC of the bank account. This is the BIC of the bank where the account is held. This is also known as the SWIFT code.

Example: "QWERIN000"

bic_secondarystringrequired

The local routing code or domestic clearing code of the bank account. For reference, this is the IFSC code in India, SORT in UK, ABA in the US, etc.

Example: "YESB0000002"

curl -i -X POST \
  https://api.glomopay.com/api/v1/bank_account_validation \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>' \
  -H 'Content-Type: application/json' \
  -d '{
    "country": "Ind",
    "holder_name": "John Doe",
    "account_number": "987654321001",
    "bic_primary": "QWERIN000",
    "bic_secondary": "YESB0000002"
  }'

Responses

Bank account validation successful

Bodyapplication/json

idstringread-only

The unique identifier for the bank account validation.

Example: "aval_5JU9yv0lGSUP"

statusstring

The status of the bank account validation. This does not mean the bank account is valid or invalid. It means the validation process was successful or failed.

Enum"success""failed"

validation_messagestring

The message returned by the bank account validation process.

Example: "The account is registered to John Doe"

fee_chargedobject(Money)

The fee charged for the bank account validation process.

Response

application/json

{
  "id": "aval_5JU9yv0lGSUP",
  "status": "success",
  "validation_message": "The account is registered to John Doe",
  "fee_charged": {
    "amount": 1000,
    "currency": "USD"
  }
}

List all bank account validations

Request

Security

JWT

Query

beneficiary_account_idstring

The ID of the beneficiary bank account to filter validations

Example: beneficiary_account_id=bene_5JU9yv0lGSUP

countrystring(iso-3166-1-alpha-3, case-insensitive)

The ISO 3166-1 alpha-3 code of the country to filter validations

Example: country=Ind

beforestring(timestamp)

ISO-8601 timestamp in UTC to filter resources created before this time. Use this to avoid Page drift issue. See Pagination parameters for more details.

Example: before=2025-02-18T12:03:44Z

afterstring(timestamp)

ISO-8601 timestamp in UTC to filter resources created after this time. Use this to avoid Page drift issue. See Pagination parameters for more details.

Example: after=2025-01-18T12:03:44Z

per_pageinteger

Number of resources per page. Should be between 1 and 100.

Default 20

pageinteger

Page number for pagination. Starts from 1. Get the next page number from the next field in the response.

Default 1

curl -i -X GET \
  'https://api.glomopay.com/api/v1/bank_account_validation?beneficiary_account_id=bene_5JU9yv0lGSUP&country=Ind&before=2025-02-18T12%3A03%3A44Z&after=2025-01-18T12%3A03%3A44Z&per_page=20&page=1' \
  -H 'Authorization: Bearer <YOUR_JWT_HERE>'

Responses

List of bank account validations matching the filters

Bodyapplication/json

dataArray of objects(BankAccountValidation)

page_metaobject(PageMeta)

Response

application/json

{
  "data": [
    { … }
  ],
  "page_meta": {
    "current": 2,
    "previous": 1,
    "next": 3,
    "per_page": 20,
    "pages": 10,
    "count": 200
  }
}

Withdrawal

This resource represents the withdrawal transaction from your Glomo account to your withdrawal account.

Operations

Withdrawal Account

This resource represents the withdrawal account details. The withdrawal account is the bank account where the withdrawal amount will be credited.

Operations

Settlement

This resource represents the settlement details. The settlement is the process of transferring funds from your Glomo account to your bank account.

Operations

API specification for Glomo (1.0.0)

Balance

Balance Conversions

Payment Link

Orders

Customer

Document

Payment

Refund

Price

Subscription

Payout

Beneficiary

Bank Account Validation

BankAccountValidation

Validate any bank account

Request

Responses

Was this helpful?

List all bank account validations

Request

Responses

Was this helpful?

Withdrawal

Withdrawal Account

Settlement