Skip to main content
Reduce payment failures by validating customer bank details before submitting RTP or payout requests. Safepay exposes two utility endpoints under your aggregator:
EndpointPurposeKey request parameters
GET /title-fetchReturns the registered account title for a Raast IBAN.iban (query)
GET /account-infoRetrieves metadata for an IBAN or alias, optionally combining title fetch.iban or alias_* params; with_title_fetch flag
Call these endpoints before RTP or payout operations to ensure the payer or beneficiary details are valid. Cache responses briefly to avoid extra latency.
GET /account-info accepts optional JSON body parameters (iban, with_title_fetch). Use query parameters if your HTTP client does not support GET bodies.

​
Title fetch example

curl --request GET "{{base_url}}/v1/aggregators/{{aggregator_id}}/title-fetch?iban={{customer_iban}}" \
  --header "X-SFPY-AGGREGATOR-SECRET-KEY: {{secret_key}}"

​
Account info + alias lookup

Use the account-info endpoint when you only have the customer’s Raast alias. 
curl --request GET "{{base_url}}/v1/aggregators/{{aggregator_id}}/account-info?alias_type=RAAST_ID&alias_value={{customer_alias}}&with_title_fetch=true" \
  --header "X-SFPY-AGGREGATOR-SECRET-KEY: {{secret_key}}"

​
Title fetch via alias

Use GET /title-fetch/alias when you have a Raast alias and need the account title quickly.
cURL
curl --request GET "{{base_url}}/v1/aggregators/{{aggregator_id}}/title-fetch/alias?alias_type=RAAST_ID&alias_value={{customer_alias}}&with_title_fetch=true" \
  --header "X-SFPY-AGGREGATOR-SECRET-KEY: {{secret_key}}"

​
See also