4P Finance connector
The connector runs exclusively on the backend. The Magnum operator manages one global 4P credential through private deployment configuration, using FOUR_P_API_KEY. It is distinct from tenant API keys and is never returned to a business or browser. Tenant settings cannot replace or read it.
Technical contracts
| Operation | Contract or status |
|---|---|
| Create Pix | PUT /v1/pix/transaction |
| Retrieve notification | GET /v1/notification/:token |
| Indicative public quote | Magnum's independent quote sources; no provider execution guarantee |
| Off-ramp | Isolated adapter; live contract not validated in this release |
The provider's Pix payload includes the payer document, email, amount, unique reference, callback URL and custom_data.receiver_wallet. Its technical page describes a payer wallet in a P2P flow. That documentation alone does not authorize merchant settlement, third-party destinations, resale or processing several businesses under one credential.
Business receiving configuration
A business configures fixed addresses by network and matching asset through Settings and the authenticated /v1/console/workspaces/:workspaceId/settlement resource. The backend owns this configuration. The payer checkout and session-creation body cannot override the beneficiary.
The global credential centralizes technical integration only. Before any live activation, the operator must obtain express approval from 4P for the exact commercial model, eligible businesses, destination policy and enabled networks/assets. No such approval is inferred from storing a credential or an address.
Closed payment policy
Live creation remains disabled. No environment value, API key, saved destination or iframe option bypasses that policy. Sandbox demonstrates the integration without creating a payable charge.
The notification pipeline durably stores callback tokens and retrieves the provider's data on the server. A documented paid state without verified settlement metadata records Pix receipt only. Destination, network, amount and transaction hash must match before crypto settlement is recorded. Unknown data is quarantined and repeated events are deduplicated.
Sources
Reviewed November 4, 2026: credentials, transaction creation, notifications, and networks. These technical contracts do not replace an applicable commercial agreement.
Supplier terms must be checked against the actual contracted service and any written authorization; technical integration examples do not replace that agreement.