Integrate 1BILL

Build reliable 1LINK 1BILL integrations without confusing 1BILL with 1GO/Raast P2M, 1IBFT, a card gateway, or an unrelated product named OneBill.

First: inspect and classify

Always inspect the repository before planning or writing code. Search for 1LINK or 1BILL SDKs, clients, URLs, credentials, biller prefixes, PSID or consumer-number generation, inquiry/payment/void/status handlers, schemas, database records, message signatures, settlement files, reconciliation jobs, tests, and certification artifacts.

• If an integration exists, identify its exact 1LINK product, API/catalogue version, organization role, environment, endpoints, authentication/signing scheme, and implemented flows. Repair the current design with minimal disruption.
• If no integration exists, design it using the project's language, framework, data model, security, logging, job, and testing conventions.
• Never invent request fields, response codes, signatures, encryption, URLs, credentials, prefix rules, PSID length, or timeout behavior. Obtain them from the merchant's current 1LINK sandbox/certification documentation.

Determine the integration role before choosing a flow:

1. 1LINK member bank or non-bank initiator consuming 1BILL APIs;
2. billing entity exposing or connecting billing data for collection;
3. government or institutional collection through an approved partner;
4. merchant actually seeking 1GO/Raast P2M or card checkout rather than 1BILL.