Use saved bank details

7 min

Use this flow when you have already collected and stored a supplier’s bank account and want to send funds without collecting their details again.

This is the standard approach for vendor payouts, contractor payments, refunds, or any recurring disbursement workflow. Once a bank account is securely stored and associated with a contact, you can initiate credits using its identifier.

No additional bank details are required at payout time.

Prerequisites

Jetpay API Key

Your company bank account ID where funds will be deposited

An existing Jetpay Contact IDContact

A saved bank account for that Contact

Flow overview

sequenceDiagram
    participant Platform Backend
    participant Jetpay API

    Platform Backend->>Jetpay API: PUT /credit (amount, contact_id, to_bank_account)
    Jetpay API-->>Platform Backend: Credit created (processing)

    Jetpay API-->>Platform Backend: Webhook: credit status updates (initiated, completed, etc.))

Implementation details

Create a credit

Endpoint: PUT /credit

Use your contact ID (contact_id), your contact's bank account ID (from_bank_account) and your merchant bank account ID (from_bank_account) to create a credit transaction.

BASE_URL="https://extapi.demo.jetpay.baselinepayments.com"
API_TOKEN="<YOUR_API_TOKEN>"

curl -X PUT "$BASE_URL/credit" \
  -H "Authorization: Bearer <YOUR_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 10000,
    "statement": "Supplier Payout",
    "note": "Invoice 4821",
    "from_bank_account": "platform_bank_abc",
    "to_bank_account": "bank_456",
    "contact_id": "contact_123"
  }'

Handle the response

If the credit is successfully created, a response will be returned with an HTTP status code of 200 and the following response body:

{
  "identifier": "credit_123",
  "link": "http://example.com",
  "amount": 10000
}

There is no further step to take once the credit is successfully created.

Track status updates via events/webhooks

As the transaction moves through its lifecycle, an Event is created for each state update. The most efficient way to track these updates in your system is to register for webhooks. If you are not yet familiar with our webhooks system, please review the Events and webhooks guide.