How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Interchecks Payments API

The Payments API from Interchecks — 7 operation(s) for payments.

Interchecks Payments API is one of 16 APIs that Interchecks publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 8 operations across 7 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.

Requests are made against 2 base URLs: http://example.com, https://test.api.interchecks.io.

8 operations 7 paths 2 schemas 6 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2
Base URL
https://prod.api.interchecks.io
Authentication
HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 2

Interchecks Payments API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (httpBearer). It supports OAuth 2.0 (sec0).

Paths & Operations 8

Across 7 paths, the API surfaces 8 operations — 6 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 8
POST
/api/v2/{payer_id}/payments
Create Payment
CreatePayment 2 params body → 200
PATCH
/api/v2/{payer_id}/payments/{payment_id}
Update Payment
UpdatePayment 3 params body → 200
GET
/api/v2/{payer_id}/payments/{payment_id}
Get Payment by ID
GetPaymentbyID 3 params → 200
GET
/api/v2/{payer_id}/payments/reference/{payment_reference_id}
Get Payment by Reference ID
GetPaymentbyReferenceID 2 params → 200
GET
/api/v2/{payer_id}/payments/{payment_id}/transactions
Get Transactions by Payment ID
GetTransactionsbyPaymentID 2 params → 200
GET
/api/v2/{payer_id}/payments/reference/{payment_reference_id}/transactions
Get Transactions by Payment Reference ID
GetTransactionsbyPaymentReferenceID 2 params → 200
GET
/api/v2/{payer_id}/payments/reference/{reference_id}
Get Payment by Reference ID
get-payment-by-reference-id 2 params → 200
GET
/api/v2/{payer_id}/payments/reference/{reference_id}/transactions
Get Transactions by Payment Reference ID
get-transactions-by-payment-reference-id 2 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are CreatePaymentRequest (2 properties), UpdatePaymentRequest (1 property). Each schema is shown below with its type and property counts.

CreatePaymentRequest
object
2 properties 2 required
UpdatePaymentRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

interchecks-payments-api-openapi.yml Raw ↑

Other APIs Interchecks publishes across the network.

Interchecks Accounts API
Interchecks Authentication API
Interchecks Oauth2 API
Interchecks Payers API
Interchecks Payload API
Interchecks Payment Accounts - Bank API
Interchecks Payment Accounts - Card API
Interchecks Payment Accounts - PayPal API
Interchecks Recipient Emails API
Interchecks Recipient Verification API
Interchecks Recipients API
Interchecks Reports API
Where this information came from

This is an independent, third-party profile of Interchecks Payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.