Paymish Loading Docs Preparing guides, collections, and live API references...
Paymish Docs

Update customer

Topics

Endpoint Overview

Customers

Update customer

**Complete URL:** `PUT https://api.paymish.com/api/transaction-service/external/v1/customers/{id}`

PUT /api/transaction-service/external/v1/customers/{id} Requires authentication

Purpose

Use this endpoint to update customer. It belongs to the Customers collection and is designed for backend integrations.

Request shape

0 parameters and 0 documented body fields using application/json.

Implementation Guide

Recommended workflow

1

Authenticate first and inject a valid bearer token or secret key before calling the endpoint.

2

Validate the input data, identifiers, and account state in your application before making the request.

3

Send the PUT request from your backend using the required headers and the expected content type (application/json).

4

Persist the important identifiers returned in the response so later lookups, webhooks, or support actions can be linked correctly.

Implementation notes

  • Protect state-changing operations with strong validation, logging, and retry rules to avoid duplicate mutations.

Expected Outcomes

200

Success example

The request is accepted and you can store the returned identifiers for later reconciliation.

Representative Response 
{
  "status": "success",
  "message": "Request processed successfully",
  "data": {
    "reference": "PM-REF-12345"
  }
}
400

Failure example

The request is rejected because a required input is invalid or missing.

Representative Error 
{
  "status": "error",
  "message": "Invalid request payload. Check `required_field` and try again.",
  "errors": {
    "required_field": [
      "`required_field` is required."
    ]
  }
}
After the response:
  • Log the Paymish reference or request context returned by the API so support teams can trace the call later.
  • Retry only when the failure is safe to repeat; otherwise correct the payload or auth state first.
  • Store enough internal metadata to match the API response back to your order, payout, case, or checkout record.

Language Notes

Python

Use `requests` from a backend worker, service, or Django/Flask app and centralize headers in a reusable helper.

Node.js

Use `axios` or `fetch` from Node.js services only; do not place secret credentials in frontend bundles.

PHP

Wrap cURL usage in a small client class so auth headers, error handling, and logging stay consistent.

cURL

Use cURL for smoke testing and debugging, then move the final logic into your backend service code.

This endpoint does not currently expose structured parameters or response metadata in the imported specification.

Code Examples

Python 
import requests

headers = {
    "Authorization": "Bearer YOUR_SECRET_KEY",
}
response = requests.put(
    "https://api.paymish.com/api/transaction-service/external/v1/customers/{id}",
    headers=headers,
)

data = response.json()
print(data)
Node.js 
const axios = require("axios");

const response = await axios({
  method: "put",
  url: "https://api.paymish.com/api/transaction-service/external/v1/customers/{id}",
  headers: {
    Authorization: "Bearer YOUR_SECRET_KEY",
  }
});

console.log(response.data);
cURL 
curl https://api.paymish.com/api/transaction-service/external/v1/customers/{id} \
  -X PUT \
  -H "Authorization: Bearer YOUR_SECRET_KEY"
PHP 
<?php
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://api.paymish.com/api/transaction-service/external/v1/customers/{id}");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "PUT");
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "Authorization: Bearer YOUR_SECRET_KEY",
]);

$response = curl_exec($ch);
curl_close($ch);
$data = json_decode($response, true);
print_r($data);
Previous endpoint Get customer Next endpoint List payment pages