The Resolve Customer endpoint allows you to verify that a payment alias is valid and belongs to an active customer. This is a critical step when building flows where users enter an alias to send or request payments, especially in push payment scenarios. Before submitting a payment, you can use this API to confirm that:
  • The alias exists
  • The associated customer is currently active
  • The customer’s metadata is accessible (e.g. whether they are an individual or a business)
Using this API early in your payment flow can help reduce failed transaction attempts and improve your user experience. For example, if a user types an alias into your app, you can resolve that alias to validate the recipient and potentially surface their display name or business name before the payment is submitted.

​
When to Use It

  • Push Payments: Before a user sends money, verify the recipient’s alias.
  • Pull Payments: Before requesting payment from a customer, confirm that their alias is active and valid.
  • Risk & UX Decisions: Retrieve additional metadata (like whether the customer is a business) and tailor your flow accordingly.
  • Avoid Preventable Failures: Prevent unnecessary calls to the Payments API that would otherwise fail due to inactive or non-existent aliases.

​
Resolve a Customer

Resolve customer
curl --request GET \
     --url https://sandbox.paylias.xyz/gateway/api/v1/csp/customer/{payment_address}/resolve \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --header 'x-paylias-api-key: <API-KEY>' \
     --header 'x-org-id: <Org-ID>' \
     --header 'x-partner-id: <Partner-ID>' \
response
{
  "data": {
    "created_at": {
      "seconds": 1743092228
    },
    "first_name": "Ziyad",
    "last_name": "Parekh",
    "nick_name": "ziyad",
    "partner_id": "part_ct23b6420or249k5boag",
    "payment_address": "ziyadparekh@safepay-platinum",
    "status": 2,
    "token": "cust_cvink1420or763mhjesg",
    "updated_at": {
      "seconds": 1743092228
    }
  },
  "ok": true
}
Replace {payment_address} with the alias you wish to resolve (e.g. ziyadparekh@safepay). By resolving an alias before attempting a payment, you not only improve reliability but also enhance confidence and security for your users. This API acts as the first touchpoint for validating intent and building trust into your payment flow.