SatchelPay
Supports in this guide: Payouts
Provider website: satchel.eu
What you need to do for start processing transactions (brief summary)
- Get your credentials (from SatchelPay)
- Connect in Dashboard
- Send an API request
Prerequisites: get from SatchelPay
Contact your SatchelPay account manager to get your account verified and receive the following credentials.
- API key -> Corefy field
api_key. - Account number -> Corefy field
account_number.
EUR only, via SEPA credit transfer.
Payouts processing (connect Provider account, create payout-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open SatchelPay in the provider directory and press Connect at SatchelPay Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- API key
- Account number
- Test Mode -> (enable if you are using sandbox credentials)
Success
You have connected SatchelPay Provider account!
First request to Corefy API (MIN)
What it does: creates a payout-invoice via SEPA credit transfer to an individual beneficiary.
Payout - MIN
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "6f1a2b3c-4d5e-4f6a-8b9c-0d1e2f3a4b5c",
"service": "sepa_credit_transfer_individual_eur",
"currency": "EUR",
"amount": 100,
"customer": {
"reference_id": "cus_123"
},
"fields": {
"iban": "DE89370400440532013000",
"first_name": "John",
"last_name": "Doe",
"descriptor": "Payout"
}
}
}
}
Important
fields.ibanis always required.- For an individual beneficiary, both
fields.first_nameandfields.last_nameare required; for a company beneficiary, sendfields.company_nameinstead (use thesepa_credit_transfer_company_eurservice) - whichever pair is missing causes a request-validation error at SatchelPay. fields.descriptoris always required (sent to SatchelPay as the payment narrative).- SatchelPay always receives a hardcoded beneficiary address regardless of what you send -
address,city, andzipCodeare always sent as the literal string"not provided", andcountryCodeis always sent as"NP". Corefy does not currently collect or forward a real beneficiary address for this connector.
Payout - MAX
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "9a8b7c6d-5e4f-4a3b-9c2d-1e0f9a8b7c6d",
"service": "sepa_credit_transfer_company_eur",
"currency": "EUR",
"amount": 500,
"customer": {
"reference_id": "cus_456"
},
"fields": {
"iban": "DE89370400440532013000",
"company_name": "Acme Corp",
"descriptor": "Invoice #42 payout"
}
}
}
}
Extended request (MAX)
Why add extra fields (typical reasons): - Provide additional details required by the selected service - Include optional fields required by your specific flow
Refunds
SatchelPay does not support refunds - this connector only implements the Payouts side.
Additional info
- Two-step payout flow - Corefy first creates the payment at SatchelPay (
invoke), then confirms it in a separate step (process); a payout only completes once both steps succeed. - Active reconciliation is available - Corefy can poll SatchelPay's transaction history to refresh a payout's status.
- No Payments, no recurring - this connector only implements Payouts; there is no card/HPP flow and no token saving.
- Live vs. Test Mode use different SatchelPay environments - credentials and balances are environment-specific.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the API key and account number for the selected environment (
test_mode) - Payout rejected for missing beneficiary details ->
fields.ibanandfields.descriptorare always required; also send eitherfields.company_nameor bothfields.first_name/fields.last_name, matching the service you selected - Currency or service is not supported -> SatchelPay only supports
EURvia SEPA credit transfer - Refund fails -> SatchelPay does not support refunds through Corefy
Question
Still looking for help connecting your SatchelPay account? Please contact our support team!