Plutio integration

Connect Bookkeeping → Integrations → Plutio using your own API client and select the workspace to use. Import invoices, approve crypto payment links, separately record confirmed payments, or create unsent invoice drafts. Collection, payment recording, draft creation and notifications start disabled.

Connect a workspace

1. In Plutio, open Settings → API manager and create a named API client. Enable the intended workspace for that client. Keep the client ID and secret private. See Plutio API client management.
2. In MakeCrypto, select Connect on the Plutio card. Enter the workspace subdomain, client ID and secret, then check the credentials. This uses merchant client credentials and does not require a MakePay-owned OAuth app.
3. Select the returned active workspace and confirm its name, currency and time zone. A client may access several workspaces; choose the specific workspace for this connection.
4. Review imported invoices before enabling payment options. Enabling a capability requires a fresh workspace check and confirmation. Payment recording also has a separate acknowledgment of Plutio's native payment and receipt behavior.

Credentials are stored encrypted and are not returned in connection summaries. Plutio scopes client access by workspace. Its webhook event checklist does not provide read-only REST access or limit the API to invoices. Access and permissions must be appropriate for the actions you enable.

Collect payment for an existing invoice

Enable Create crypto payment links for invoices. Choose an eligible ordinary sent invoice and review its current balance. Approve the original MakePay link and share it with the client. The approval retains that workspace, invoice, amount and time window. Creating a link does not edit the native invoice or send an email for you.

Opening the link rechecks the original invoice and connection. A changed balance, conflicting payment or expired approval may stop new checkout instructions. A qualifying confirmed payment pairs with its original invoice in Bookkeeping. Pairing does not itself record a native payment in Plutio. Late or ambiguous payments retain their original history for review.

Native drafts, recurring or split arrangements, archived/cancelled/deleted invoices and unsupported amounts are unavailable for public collection. Configure MakePay settlement before sharing links.

Record a received payment separately

Enable Record received MakePay payments and acknowledge the native payment/receipt behavior. Choose a confirmed production MakePay source and its original eligible Plutio invoice. Review the current invoice, source, same-currency fiat amount and remaining balance before explicitly approving recording. A payment already owned by another original operation cannot be reused.

The connector applies one whole source amount to one invoice within its balance. It can partially pay an invoice but does not divide one source among invoices. An eligible zero-paid native draft can receive a separately reviewed payment without becoming eligible for public collection.

Plutio's recording action creates a manual payment and native receipt. MakePay's qualified API request supplies invoice identity and amount. It does not select a historical native payment date, bank account, payment method or receipt-email setting. Review Plutio's own behavior before enabling recording; see manual payments.

Optional automatic recording on one original invoice link

Before the original invoice link is paid, separately review and authorize its future recording rule. Confirm that exact invoice, original fiat amount, payment window and native receipt behavior. Enabling the connection option or approving collection alone does not save this rule.

Only a qualifying first confirmation after authorization and within the original link's window can prepare automatic recording. Changed native evidence or a late/conflicting source needs individual review. Pause the rule to stop unstarted recording. Pausing cannot undo a request already sent or erase received money. Original verification remains available after pause or disconnect.

Create an invoice draft from an unpaired payment

Enable Create invoice drafts from unpaired payments. In Invoice creation, choose a confirmed payment with its original supported fiat value and an existing Plutio company or individual client. Enter one line item and, optionally, a due date.

Review the server preview, full customer, original source and saved fiat value. Explicitly approve the source/customer and the single untaxed item. Creation uses quantity one and verifies the resulting zero-tax, zero-discount totals. The new invoice stays an unsent draft. MakePay does not send, email or finalize it.

Draft creation and item attachment are separate native phases. Use the original creation history if either needs review. An identified draft with an unstarted item can receive a fresh approval for that same item after the earlier authority expires. An item already attempted has verification controls instead of another attachment request. Recording the received payment against a completed draft requires a separate approval.

Optional rules for future invoice drafts

Open Invoice rules → New invoice rule. Choose an active company-owned one-time MakePay link, its existing Plutio customer and one untaxed item. Enter an exact minimum and maximum per payment in the link's fiat currency.

Total amount, invoice-count cap and end date/time are optional. Leave them empty to continue until paused; the payment link's own expiry still applies. Review the complete policy and approve both consents before enabling the rule. A setting alone creates no automatic invoice.

Only future confirmed payments on that exact link qualify. Each must have its original saved fiat evidence and first confirmation after the rule was authorized. Existing payments are excluded. A link already belonging to another invoice/accounting connection cannot be repurposed by this rule. The connector does not infer a customer from an amount or current exchange rate.

Rules and held-payment reasons have paged history. A payment outside policy or missing qualifying evidence stays available for individual review while later eligible sources can continue. A reached count or total cap does not silently expand authorization. Pause the original rule before reviewing a replacement policy. Changes to its financial link scope, credentials or native workspace configuration require a new review.

Notifications, sync and original recovery

Optional MakePay notifications cover invoice pairing, payment recording, completed drafts and sync/review problems. They start off and are deduplicated. A notification failure retains a retry without repeating a native financial request. Plutio's independently configured automations still apply.

Sync and the scheduled worker process bounded batches; there is no fixed completion time. Native histories that are incomplete, changing or too large for a complete observation require review. Imported data alone never authorizes a financial action.

Every operation retains its original source, authorizer, request and native identity. After an uncertain response, continue that original operation. Matching amounts alone cannot identify a receipt, and an unknown result does not authorize another financial request. Only a wholly unstarted draft/payment approval can be withdrawn. Disconnect pauses new work and preserves original histories; older connections remain accessible through the connection selector.

Supported scope

These workflows need supported original fiat evidence. Historical crypto without that record requires a separate valuation workflow and is unavailable here. Today's price, an edited link amount and a crypto or stablecoin quantity do not substitute for the payment's saved fiat principal. Flexible deposits, donations, subscriptions and wallet-only sources need separately qualified handling.

Draft creation supports one quantity-one untaxed item on an existing customer. Additional tax/template modes, new customers, native expense exports, file attachments, refunds, corrections and document sending are outside this connector's current scope. Review native documents in Plutio and use their original recovery controls before preparing another financial operation.

See the Plutio API reference and invoice creation guide.