Downloads & changelog

Downloads

File	What it is
Postman collection	Every Pay-In request, ready to run: countries, exchange rates, payment methods, create a deposit, get a deposit, re-send a notification and sandbox simulate.
Postman environment: sandbox	`base_url` = `https://sandbox-api.cashela.com`.
Postman environment: production	`base_url` = `https://production-api.cashela.com`.
Webhook signature test vectors	Cases to test your `X-Cashela-Signature` check. See Webhooks.

Import the collection and the environment you need.
Fill partner_key with your API key and partner_secret with your API secret from the Developer Portal. partner_secret is a secret variable: keep it in your local (current) value and do not share or sync it.
Run Get Available Payment Methods first, and use one of the returned payment_method codes in Create Deposit.
Add the payer fields the chosen method requires (required_fields) to the Create Deposit body (for example phone, document_key, document_number), with data valid for the deposit’s country. See Payer data & documents.
Set reference to the deposit’s reference or your external_identifier to run Get Transaction, Resend Callback and, in sandbox, Simulate Final Status.

The collection does not include the void and refund requests. See Voids and refunds.

The Pay-In API is served under /api/v1/. Its contract version (currently 3.5.0) changes independently of the URL:

Minor versions (3.4 → 3.5) are additive: new response fields, new error codes, new optional behaviour. Build your integration to ignore fields it does not know.
Major versions (2.x → 3.0) change something an existing integration can see.

For card options charged in USD, the notification amount / currency are the USD charged (for example 5.00 USD), not the local-currency invoice. Other methods are unchanged.
GET /transactions/{reference} adds details.charged_amount and details.charged_currency: what the customer was actually charged, the same figure as the notification amount / currency. details.invoice_* is unchanged and remains the invoice.
Documented: on DECLINED and CANCELLED, the notification amounts are the quote, not money that moved.

Voids and refunds are for card deposits only: other deposits answer 422 PARTNER_PAYIN_REVERSAL_NOT_SUPPORTED and nothing moves.
A full void or refund returns the whole charge to the card and keeps the Cashela fee.

Each payment method option adds document_types (accepted documents with their format) and required_fields (every field the method requires).

When the payment network refuses a deposit because of a payer field, 422 PARTNER_PAYIN_PROVIDER_REJECTED names the field in an optional provider_reason.

A compliance refusal on Get payment methods carries code: PARTNER_PAYIN_COMPLIANCE_BLOCKED.

Breaking: card.network is the lowercase network code (visa, mastercard, discover, amex), or null when unknown, in both the deposit and the notification.

Breaking: the success envelope is success, data, message. Two internal keys it used to carry were removed.

New final status REVERSED for a completed deposit whose money went back in full.
Validation 422 responses also carry success: false (status: false is kept as a deprecated alias).

Payment method options may carry availability; a deposit on an unavailable method answers 422 PARTNER_PAYIN_ROUTE_UNAVAILABLE.

New sandbox-only endpoint to drive a deposit to a final status: POST /sandbox/transactions/{reference}/simulate.

On some accounts, payment method options add data_standard, and validation errors add field_errors[].