A generic multi-client payment gateway so FlatRender, meezi.ir and bargevasat.ir can all pay through ZarinPal's single verified callback domain (pay.flatrender.ir). New Go service services/payment (clones the notification skeleton + vendored deps): - migration 31_payment_broker.sql — `payment` schema: client_apps, transactions, webhook_deliveries. - ZarinPal v4 client ported from the proven identity PaymentService (request.json -> StartPay -> verify.json; codes 100/101). - client API: POST /v1/pay/request + /v1/pay/inquiry, authed by X-Api-Key + HMAC body signature; GET /callback/zarinpal (the single verified endpoint) verifies, then 302s the user back to the site's return_url (signed) and fires a signed, retried webhook. - per-client ZarinPal merchant override (default = shared merchant); amount stored canonically in Rial, unit to ZarinPal env-configurable. - admin API /v1/admin/* (FlatRender admin JWT): client-app CRUD + key issue/rotate + transactions list. Deploy wiring: payment-svc in docker-compose.v2.yml (host port 1607), pay.flatrender.ir server block in mirror-nginx conf, ENV_FILE + README updates (cert SAN + manual migration note). Admin UI: src/components/admin/PaymentsAdmin.tsx (client apps with one-time key reveal + rotate, transactions table) + /admin/payments page + nav link + fa/en strings; pay-admin proxy route to payment-svc. Docs/SDK: deploy/PAYMENTS.md (integration contract) + deploy/sdk/flatpay.js (zero-dep Node client + webhook verifier) for meezi/any site. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
pgx - PostgreSQL Driver and Toolkit
pgx is a pure Go driver and toolkit for PostgreSQL.
The pgx driver is a low-level, high performance interface that exposes PostgreSQL-specific features such as LISTEN /
NOTIFY and COPY. It also includes an adapter for the standard database/sql interface.
The toolkit component is a related set of packages that implement PostgreSQL functionality such as parsing the wire protocol and type mapping between PostgreSQL and Go. These underlying packages can be used to implement alternative drivers, proxies, load balancers, logical replication clients, etc.
Example Usage
package main
import (
"context"
"fmt"
"os"
"github.com/jackc/pgx/v5"
)
func main() {
// urlExample := "postgres://username:password@localhost:5432/database_name"
conn, err := pgx.Connect(context.Background(), os.Getenv("DATABASE_URL"))
if err != nil {
fmt.Fprintf(os.Stderr, "Unable to connect to database: %v\n", err)
os.Exit(1)
}
defer conn.Close(context.Background())
var name string
var weight int64
err = conn.QueryRow(context.Background(), "select name, weight from widgets where id=$1", 42).Scan(&name, &weight)
if err != nil {
fmt.Fprintf(os.Stderr, "QueryRow failed: %v\n", err)
os.Exit(1)
}
fmt.Println(name, weight)
}
See the getting started guide for more information.
Features
- Support for approximately 70 different PostgreSQL types
- Automatic statement preparation and caching
- Batch queries
- Single-round trip query mode
- Full TLS connection control
- Binary format support for custom types (allows for much quicker encoding/decoding)
COPYprotocol support for faster bulk data loads- Tracing and logging support
- Connection pool with after-connect hook for arbitrary connection setup
LISTEN/NOTIFY- Conversion of PostgreSQL arrays to Go slice mappings for integers, floats, and strings
hstoresupportjsonandjsonbsupport- Maps
inetandcidrPostgreSQL types tonetip.Addrandnetip.Prefix - Large object support
- NULL mapping to pointer to pointer
- Supports
database/sql.Scanneranddatabase/sql/driver.Valuerinterfaces for custom types - Notice response handling
- Simulated nested transactions with savepoints
Choosing Between the pgx and database/sql Interfaces
The pgx interface is faster. Many PostgreSQL specific features such as LISTEN / NOTIFY and COPY are not available
through the database/sql interface.
The pgx interface is recommended when:
- The application only targets PostgreSQL.
- No other libraries that require
database/sqlare in use.
It is also possible to use the database/sql interface and convert a connection to the lower-level pgx interface as needed.
Testing
See CONTRIBUTING.md for setup instructions.
Architecture
See the presentation at Golang Estonia, PGX Top to Bottom for a description of pgx architecture.
Supported Go and PostgreSQL Versions
pgx supports the same versions of Go and PostgreSQL that are supported by their respective teams. For Go that is the two most recent major releases and for PostgreSQL the major releases in the last 5 years. This means pgx supports Go 1.21 and higher and PostgreSQL 12 and higher. pgx also is tested against the latest version of CockroachDB.
Version Policy
pgx follows semantic versioning for the documented public API on stable releases. v5 is the latest stable major version.
PGX Family Libraries
github.com/jackc/pglogrepl
pglogrepl provides functionality to act as a client for PostgreSQL logical replication.
github.com/jackc/pgmock
pgmock offers the ability to create a server that mocks the PostgreSQL wire protocol. This is used internally to test pgx by purposely inducing unusual errors. pgproto3 and pgmock together provide most of the foundational tooling required to implement a PostgreSQL proxy or MitM (such as for a custom connection pooler).
github.com/jackc/tern
tern is a stand-alone SQL migration system.
github.com/jackc/pgerrcode
pgerrcode contains constants for the PostgreSQL error codes.
Adapters for 3rd Party Types
- github.com/jackc/pgx-gofrs-uuid
- github.com/jackc/pgx-shopspring-decimal
- github.com/twpayne/pgx-geos (PostGIS and GEOS via go-geos)
- github.com/vgarvardt/pgx-google-uuid
Adapters for 3rd Party Tracers
Adapters for 3rd Party Loggers
These adapters can be used with the tracelog package.
- github.com/jackc/pgx-go-kit-log
- github.com/jackc/pgx-log15
- github.com/jackc/pgx-logrus
- github.com/jackc/pgx-zap
- github.com/jackc/pgx-zerolog
- github.com/mcosta74/pgx-slog
- github.com/kataras/pgx-golog
3rd Party Libraries with PGX Support
github.com/pashagolub/pgxmock
pgxmock is a mock library implementing pgx interfaces. pgxmock has one and only purpose - to simulate pgx behavior in tests, without needing a real database connection.
github.com/georgysavva/scany
Library for scanning data from a database into Go structs and more.
github.com/vingarcia/ksql
A carefully designed SQL client for making using SQL easier, more productive, and less error-prone on Golang.
https://github.com/otan/gopgkrb5
Adds GSSAPI / Kerberos authentication support.
github.com/wcamarao/pmx
Explicit data mapping and scanning library for Go structs and slices.
github.com/stephenafamo/scan
Type safe and flexible package for scanning database data into Go types. Supports, structs, maps, slices and custom mapping functions.
https://github.com/z0ne-dev/mgx
Code first migration library for native pgx (no database/sql abstraction).