Approve Payout

The Approve Payout endpoint is used by the Merchant to explicitly approve a payout request before it is sent for processing. This step is required only when autoMerchantApproval = 0. Once approved, the payout transitions from a pending / queued state to processing, triggering the downstream fiat disbursement.


When to Use

Call this endpoint when:

  • autoMerchantApproval = 0

  • A payout has been created and is in a pending / awaiting approval state

  • All required user inputs, KYC (where applicable), and validations are complete


Flow Context

  1. Merchant creates a payout request

  2. End user submits required details and completes KYC (if applicable)

  3. Payout enters pending approval state

  4. Merchant calls approvePayout (this endpoint)

  5. Payout moves to processing

  6. EUR is disbursed to beneficiary via Open Banking rails

  7. Merchant’s USDC balance is debited accordingly

Flow outcome:

  • The merchant initiates a transfer of USDC to the end user

  • The end user completes the off-ramp flow via the hosted widget

  • The corresponding fiat amount is made available to the end user via SEPA instant

  • The merchant’s USDC balance is debited for the corresponding amount (including applicable fees, if any)

Endpoint

POSThttps://api.tylt.money/v2/prime-fiat/instance/payout/approve

Request Headers

Name
Type
Example
Description

X-TLP-APIKEY

string

93ee3c5e133697251b5362bcf9cc8532476785t8768075616f58d88

Your Tylt API Key, used to identify your account in API requests.

X-TLP-SIGNATURE

string

d0afef3853dfc8489c8b9affa5825171fdd7y7685675e4966a05f66ed2b3eaf9462b3c9c0

HMAC SHA-256 signature generated using the API Secret Key to secure the request.

circle-exclamation

Request Body

Field Name

Type

Description

merchantOrderId

String

Bank Account Details (Payout Destination)

Use this object to capture the user’s payout destination bank account—i.e., the bank account where fiat funds will be paid out.

The following keys are reserved. If you include any of them, they will be used to pre-fill the corresponding fields in the hosted payment widget:

  • iban (string)

If a reserved field is not provided, the end user will be prompted to enter that field in the widget (if required by the flow).

Code Snippet

Response

Last updated