Examples

  • Override the response code
    • Galileo receives an authorization request and plans to approve it (the account has sufficient funds, and so forth).
    • Galileo invokes the client's Auth API webhook to see if the client wants to modify the processing.
    • The client sees the transaction amount is above a limit, and indicates the transaction should be declined with code "61" (Exceeds Amount Limit).
  • Client maintains balance
    • For some products, the client may maintain the balance instead of Galileo.
    • When Galileo gets a balance inquiry, it will invoke the client's Auth API webhook.
    • The client can respond with the balance available, in the available_balance field.
  • Client initiates transfer
    • Suppose Galileo receives an authorization request, and the cardholder has insufficient funds; Galileo is ready to decline the request.
    • But before it does, Galileo invokes the client Auth API webhook.
    • The client sees the account has insufficient funds, and initiates a transfer, by sending back the transfer_prn and transfer_amount.
    • After the transfer, the cardholder has sufficient funds, and Galileo approves the authorization.